Working lunch...
Never again
Working lunch...
Never again
Interviews are a crapshoot, and feedback from them is usually valueless. Good luck to you in your future interviews
Wow, nice hot take!
I find the concept super intuitive, like a blueprint or a mold.
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.
Is it bad programming
No, it's bad requirements, well ok maybe the programmer came up with the requirements too.
I do what the linter tells me to: https://github.com/koalaman/shellcheck
That language theory imo is pretty well shown to be very small via tests described well here:the language hoax.
Sort of with you wrt computer languages though
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 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.
In my experience only kinda, and by convention (up is on), and three-way switches break this (indicator becomes the light itself).
assuming i learned, lol :D
ECC encryption seems semi preferred now a days i thought
May be worth looking at distroless containers.
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.
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.
and feel dead inside.
Ugh, i thought this was a question, not a link. So i spent time googling for a good tutorial on floats (because I didn't click the link)....
Now i hate myself, and this post.