To me it feels like getting told to not put nice shelves in my home because other buildings don't have them.
If the claim these folks make is "time spent struggling through a default config on an unfamiliar machine" > "time saved by crafting an workshop to fit your mind", then we are not the same.
(Probably, the dividing line here is time spent coding vs time spent managing infra.)
I’ve only read The Vital Question, but I felt it was a great introduction to biochem for someone not in the field.
If the goal was simply to learn and stay sharp, then perhaps an incomplete project is a success——you did some coding, and learned something about what motivates you. If the goal was more specific, then perhaps you've (subconsciously) re-evaluated the requirements for success, and it no longer feels achievable or worth the effort.
I could be wrong, of course, but this sounds less like a problem of technical ability than one of deepening your understanding of your own motivation. If that sounds right, maybe check out https://x.com/scottdomes — I like his writing about how to identify what you want and why.
It's definitely true though that a big problem with backend is that you can't easily treat it as a whole system for test purposes.
or starting a bidding war
Remote: yes
Willing to relocate: unlikely: maybe to major metro for dream job
Technologies: Python, JS, Linux, Docker, iOS, Elm, SQL, AWS
Resume: https://www.linkedin.com/in/cameronboehmer/
Email: cameron.boehmer@gmail.com
Bachelor's in Computer Engineering, 20+ years of experience (Google, YouTube, Facebook) in consumer web doing front-end, full-stack, and systems work; would love to do ML-infra or related!