Post #3167512

@zimzat@mastodon.social @raganwald@social.bau-ha.us "osmosis" his hard for me. I'm a senior dev, but was this year hired on to an org and failed out bad. They "assumed senior level assets would just pick up their model and methods by osmosis" Well... The "model" was clearly a mix of various stages of fixes for various vintages and current failings, unequally spread throughout the codebase. No real best practices. The current operations kept failing for clear reasons of capacity and failure to adjust for grown requirements. Designers for bulk monolithic operations don't scale when the whole process routinely exhausts all available memory and takes down any adjacent process. Even a senior coming into a very startup-like structure, will need to be guided into the role, allowed to adjust to the shitshow that is the multi-generarational family of failure modes on exhibit, and can't effectively start making things "awesome" rock star style, on day two. Especially when there are hidden traps of untouchable devs you never see.