coding-saints

This is amazing. I am (regretfully) the introverted one in the community that watches as my wife and kids make the most of it. This is something I would love to stumble on. Great read!

I'll add that it was never common in my experience to get "real" details during the interview process from team members regardless of using a recruiter. Maybe it's only with my background, but I find out an actual impression the first week (processes, cross team interaction, gossip).

Besides all the "hacker games" I would play in obscure parts of the web, leisure suit Larry is one of those games I stumbled upon as a youth looking for anything that went against the grain. I was a kid that thought nudity was amazing. Still, the mechanics built into searching for clues in an environment that attempted "open world" concepts honestly consumed more time then the rewards earned.

Also Sony launched Matrix MMO that died out but I loved how they at least tried to continue character stories that added depth.

My parents owned a mom/pop video store during my childhood. It's still crazy to look back at how in-demand VHS tapes were. We lived in a super small town so there was zero competition. Cable was not common in every home yet. "Be kind, rewind" cost a buck if forgotten. Rewinding to the beginning of VHS tapes was honestly so long that nobody really forgot. The store was eventually acquired by some regional chain, and almost like magic the future started taking its form. So cool to see this.

Working on teams large and small, it's an effort. Larger companies block chunks of time to discuss this subject. Start-ups prioritize customers. One suggestion is to take ownership over tackling tech-dent or documentation. Express to your immediate team what you want to accomplish and provide some generic process to implement. It's never easy but make the effort to at least attempt solving this. Good luck!

Great book

This site was amazing when I started front end development. I remember checking in from time to time and finally seeing the blunder with DO. DO was another starting point for me in my career when I was learning servers. Sad to see this outcome.

Not seeing any logs or place for updates on this. Curious what happened.

Thank you for sharing.

My book is in context of changing career over to software engineer... "SOFT SKILLS" by John Somnez. Not sure if there's any alternative today for self taught people, but this book released right when I had started obtaining real work. Obviously just my personal experience.

I love I can still unexpectedly find a post that reminds me of why I even decided to focus on tech-related career. Great article! For me, following you down the rabbit hole is better than the result. Thanks.

Strict policy for college degree here, fyi

I want to add that while the complexities of building a PC or understanding fundamentals of open source and licences is steep... For anyone who wants these constraints but is unwilling to be curious enough to learn the ways of DIY/makers is gonna get smashed on this forum IMO. I would hope to see a sub-thread of OP asking for "advice" on how to achieve a solution solo (unless I missed it...) . I am a huge advocate for [devs] building their own PC's for fundamental understandings..