Oddbean new post about login | logout TBH sometimes devs have so much to do they are literally afraid to check prior work and find anything wrong because it will increase their stress and strain their deadlines 🫨 its literal anxiety
Then they need better project management. 🤷♀️ Software development has never not been stressful.
It's only stressful because they keep moving ahead when they still have bugs left behind.
Dragging entire cartloads of technical debt behind them and when you point to it they get pissed off because they're stressed out. But they don't want to stop because they get paid on delivery, not on quality. Because they people who are paying them actually don't care if the stuff works. 😂 But we can all see that nobody is using their app. We can't use it. It doesn't work.
I blame react ⚛️
A lot of Nostr devs use Svelte, it seems.
Then I blame JS in totality
I can agree with that.
Yeah, JS is...well it's JS.
This is why I Go... With a sprinkle of HTMX
I might attempt desktop UIs in C++ for a project...we'll see
Precisely. JS and all of its frameworks. HTMX gives 95% of all the functionality of JS, 95% confusing bloated functions I no longer have to write. Just need JS for some animations and switches. And MOST of that is just animation...
I need to start looking into HTMX more seriously. While I'll talk crap, I feel like a JS is a necessary evil at this point, it's just a huge percentage of the job market now.
HTMX.org You must learn to handle everything server side. HATEOAS Think differently. It weird at first, and the longer you've been using JS traditionally the harder it's going to be to re-wire your brain to program that way. It seems wrong at first but then the code base is so much smaller and less worry about how the client behaves because most compute is server side.
This is why Agile software development is a thing. It's saying "we'll get there when we get there, because we're doing it right." Deadlines are antithetical to Agile.
the hardest thing with deadlines and dev is that architecture is hard to measure without years of experience at actually implementing feature sets very often marketing is in charge of feature sets and architects rapidly turn grey and drop dead of heart attacks by deadline that is, if the architects are actually qualified, and IMO, software architects can only be called qualified after 10 years working as an engineer there is no magic trick learning how to spec out a project without getting into overruns and quality problems due to deadlines and unrealistic expectations of management
Well, that's why architect is a real job. 🤷♀️
yeah but most of them are like 3 years CS and 2 years writing waffly documents and get hired to direct work they don't understand
for real, i've seen this at a shitcoin job, the "architect" was really a marketing guy in disguise
i'm getting close to being able to do it now, but i've been working mostly full time since 2018 nothing like failing to build the features you thought you could build to teach you prudence in architecture... where building architects must learn to work with material and space, software it's about time and brains
We've got that at my day job right now. The deadline is artificially imposed by the big trade show, the research and product teams take their time in figuring out what they want to debut at the trade show, they ask the devs to do it, the devs say "there's not enough time before the trade show," and chaos ensues. 😅
No incentives to verify, and then we get this: https://theconversation.com/what-allegations-of-alzheimers-research-fraud-mean-for-patients-187911 in one sense - Cuz pROgrEs and ImPaKt. in another sense, the science version of working with old code and the related thread. Those are just two possible reasons that come out of a very entangled situation of bad incentives. nostr:nevent1qqsxflkppfmfz838zga5q8gqfp9y4gvgmu8yujhphknkkqvfmwap2kspr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpsrqsqqqqqpsaa8tl
