116 karma · joined September 15, 2019
As author wrote: we need to practice the benefit of the doubt. Or I like the “trust but verify” pattern
Because companies resent that they have to take on risk and pay people to extract value from the market.
Ugh, why do we have to pay people to code, maintenance, etc. Lets pay people to extract more value for our bonuses and shareholders. Lets try to only hire heavyweights so that we don't get hung up on that difficult-to-measure coding process, knowledge transfer, messy human-ness. Oooh how nice, we can hire a fewer employees that know how to leverage code agents that free them up to think about that what REALLY matters...
When I was less self aware, I'd say similar things: my coworkers/manager can't accept that I write perfectly good code at a faster pace. Doesn't matter whether it's good or bad code-- the coworkers have to collectively understand it in order for it to be maintainable.
I get to vote and he does not.
Edit: s/green card/H1B/
Vibe coding existed long before AI, especially in web/startup/enterprise information systems. You don't need to be a critical thinker to make a successful RoR app.
Finding the data on this would be convenient but its still unclear to me. I'm not a fan of how that article from NU cites its sources loosely, including lazily citing Wikipedia.
https://how-nostr-works.pages.dev/
I find that example pretty humorous... Damn, what kind of controversy is Pamela spreading?
I like it but feel nervous that there is synergy with the bitcoin space. Hype and validation is thick in that space
What does bipartisan even mean? I've seen my state lose a republican congressperson who, while I disagreed with, called out trump on disrespecting branches of gov during first term and since been replaced with a pro-trump congressperson. The checks and balances are eroding and the citizen response has to be strong.
I've also been checking out CrowdSec. I appreciate it's modular architecture but it definitely deviates away from the folks that just wants to expose an HTTP service and get on with their lives. I've enjoyed the Caddy server for this reason, but yeah, not as secure-as-default when it comes to attacks a WAF would mitigate.
I worked at a place that did this with their frontend app. Devs rarely knew where anything should go and so for any given Component/Module, there was usually some accompanying `MyComponent.fns.ts` file. Homes were NEVER found for it later. Code duplication through the nose and lots of spaghetti coupling.
Edit: i'm definitely blowing off some steam. That said, I think there is good virtue in this "habit" so long as there is good reason that it "doesn't fit anywhere" ... and when another module starts referencing the temporary home module, it is a smell that the time is now to give it a proper home.
I doubt such thing is sustainable in average software dev gigs but I'll keep trying.
Joining a neurodivergent support group has been great; meet some similar minds.
All said, maybe it is a larger issue and working from the office is just addressing symptoms that are more apparent when going remote. Are we really missing out on those water cooler talks or is there a missing information/management role. I think of how I've had the conversations with other teams around the occasional virtual water cooler "oh, you're building a microservice to do that... so are we.... why are we building the same microservice?"
Looks like there are some here https://www.techscribe.co.uk/techw/asd-simplified-technical-...