• 0 Posts
  • 20 Comments
Joined 11 months ago
cake
Cake day: July 29th, 2023

help-circle



  • I’m very lazy so I’d probably start by looking at filters on those sites, if i really wanted to tackle this with programming, i’d:

    see if there’s an api, or rss feed for these sites, if so i’d pull that down with a cron job and do filtering locally with probably regex.

    if not i’d scrape the html and pull out the relevant links with whatever the latest html parser is for the language i use (i.e. it used to be beautiful soup for python, but there’s i think a new better one).

    but as i said i’m rather lazy, and haven’t been on the prowl for jobs for some time.







  • I hear this quite a bit, and think there’s actually a good deal of nuance to it. I’ve seen places that insisted on comments for everything, and it was silly, a significant number of comments had no value. This made people not read comments, as opposed to other places I’ve worked with very few comments - when you ran across a comment you gave it more weight (something here was complex, or not as simple as it seemed).

    So imo, use comments which can communicate effectively, but use them sparingly for important parts that are complicated, for the rest attempt to communicate with the code itself.



  • For my local team: Generally a container (docker) for local dev. My team uses go so sometimes a Makefile without docker is enough. For other teams i’ve mostly i see docker.

    for multiple apps this can get more complicated, docker compose, or skaffold is what i generally reach for (my team is responsible for k8s clusters so skaffold is pretty natural). I’ve seen other teams use garden.

    hashicorp makes something called waypoint which i’ve never used. Nix people seem to be well liked as well.


  • I think of OOP as encapsulation, abstraction, and polymorphism primarily. Inheritance is definitely taught as part of it, but it seems like most people have found that to be the least used part of it.

    It seems like you understand oop, but find it overrated, from your post it sounded like you didn’t understand it – but maybe you meant you didn’t understand it’s popularity.




  • Personally i prefer go, but these are pretty standard languages; so learning the in’s and out’s really isn’t all that time consuming (you aren’t going to have to change how you think about programming like say rego). Since you have python experience these should be no big deal, but maybe worth playing with a bit if you are trying to get a job in either language and need to cross off that bullet.

    As for expanding your learning, i’d try something like functional programming (haskell), or query language like rego above. Neither of these will be great for your resume though.