Boot.dev Blog

I highly disagree with the interfaces criticism.

Firstly You can literally just use one of the dozens of go lsps or code tools to search for API invocations to find what structs are passed/called into it. More importantly if you need to know you've written bad code. The entire point of an interface is that you SHOULDN'T need to know the underlying type. If you do you've violated the entire point. Just pass concrete ones. I've written Go for years and never had a problem with this, even in large open source projects like Kuberenetes.

Secondly, the criticism about flipping return values order/meaning isn't a criticism of interface being structurally typed (https://en.wikipedia.org/wiki/Structural_type_system). If you return int, int and the second int "should be even", you should have defined a type "Even" and returned int, Even*. Systems which are structurally typed can demonstrate functional extensionality and (https://github.com/FStarLang/FStar/wiki/SMT-Equality-and-Extensionality-in-F%2A) and check whether you've flipped the arguments, which would be a more valid criticism (but such checks are expensive and conflict with compile time requirements). Also Java has the same problem, if you define two interfaces with the same method signature and a single class implements both you can't disambiguate.

Thirdly, the structural typing has a huge advantage, namely looser coupling and more tightly defined interfaces. If you follow the "accept interfaces return structs" go idiom,…

While people are right to point out the down market, I think they're ignoring the obvious corollary. My theory is that you've been getting by with the weaknesses in your resume because the tech market hasn't seen a major downturn for awhile. From skimming your blog, it doesn't seem like you're an unskilled developer, but that's how your resume presents you.

Others pointed out that you don't mention impact, just responsibilities, and this is 100% the thing you need to fix. Apologies for the handwaving with somewhere (read this on my phone, replying on my desktop), but somewhere you said you were thinking like a dev and someone else backed you with a "we're not MBAs". I strongly encourage you to drop this dichotomy from your mental model. You should be curious about the impact of your work, whether it's to benefit the business, your coworkers, or some technical process. Your resume reads like that of someone who did what they were told and not a lick more. I've worked with people like that and I cannot give them ownership over projects. You're selling yourself as a liability.

But there's good news, judging from your blog you have had impact, so it just comes down to figuring out how to sell it. (sidebar: everyone is in sales, in this case you are selling yourself, this shouldn't make you uncomfortable, just think of it of making it easier for hiring managers to say "yes, I would like to take to this person / take a chance on them / think they will do well on the…

Boot.dev | Junior Video Editor/Animator | REMOTE (US/Europe Timezones Preferred) | Full-time | https://www.linkedin.com/jobs/view/3987534709

At Boot.dev we're building the smartest way to master backend development by tackling the hardest problem with e-learning: boredom. We’re a small team of developers who love to make the process of learning as fun and hands-on as it can be.

We are looking for a junior video editor/animator that can help us more consistently and quickly produce computer science and programming explainer videos. We don't need someone with tons (or any) paid professional experience, but we do want to see a portfolio of what you can do!

Link to full JD: https://blog.boot.dev/careers/#junior-video-editoranimator