tech management heads are like "ai is so amazing, this team went from idea to closed beta in three months" like that wasn't just normal velocity for a greenfields project at one point
-
some of us have been around long enough to remember a time when you could make an app in a weekend with Ruby on Rails TM
@hailey whats changed since then? i feel like those tools are still around its just not How Things Are DoneTM anymore
-
@hailey whats changed since then? i feel like those tools are still around its just not How Things Are DoneTM anymore
@a_mi yeah I think the fashion moved on. particularly re JS heavy apps where there is famously so much project config bullshit to endure, every JS app is a bit different, no big framework with strong conventions ever took off
-
@a_mi yeah I think the fashion moved on. particularly re JS heavy apps where there is famously so much project config bullshit to endure, every JS app is a bit different, no big framework with strong conventions ever took off
@hailey probably also everything being walled into saas and cloud services with competing standards
-
tech management heads are like "ai is so amazing, this team went from idea to closed beta in three months" like that wasn't just normal velocity for a greenfields project at one point
@hailey idea to closed beta is like a weekend project for me.
-
@a_mi yeah I think the fashion moved on. particularly re JS heavy apps where there is famously so much project config bullshit to endure, every JS app is a bit different, no big framework with strong conventions ever took off
-
@knack @a_mi @hailey Many fashionable org scale problems to blame here, too. The rise of "front end" vs. "back end" teams, "federated" processes for organisations at a scale 1/100th of the size of orgs that need it, dedicating teams to build complex infra solutions on top of cloud systems whose providers already offer out-of-the-box solutions for that problem, etc.
-
@hailey whats changed since then? i feel like those tools are still around its just not How Things Are DoneTM anymore
@a_mi Over-hiring, making everything a process, requiring formal meetings, requiring formal management artifacts, needing lots of teams to weigh in on everything, and "oh hey, hold off on that for now..." as soon as any real momentum is created
-
@knack @a_mi @hailey Many fashionable org scale problems to blame here, too. The rise of "front end" vs. "back end" teams, "federated" processes for organisations at a scale 1/100th of the size of orgs that need it, dedicating teams to build complex infra solutions on top of cloud systems whose providers already offer out-of-the-box solutions for that problem, etc.
@duncan_bayne @knack @a_mi @hailey and here we see meta-theory building. As someone who has spent much of his career trying to evangelise a new approach to (theory for) group theory-building, in the form of semantic modelling, I can assert that it is much more difficult to explain a new way for groups to understand each other than merely to adapt a new development approach
-
@duncan_bayne @knack @a_mi @hailey and here we see meta-theory building. As someone who has spent much of his career trying to evangelise a new approach to (theory for) group theory-building, in the form of semantic modelling, I can assert that it is much more difficult to explain a new way for groups to understand each other than merely to adapt a new development approach
@cliffordheath @knack @a_mi @hailey I've seen some of your work in this area @cliffordheath and it's mind blowing (in a good way).
A challenge I repeatedly run into is organisations who literally do not care about correctness. Not just "we'll gradually work towards it as budget permits" but literally do not see why it's important to correctly model their business domain in their own software 🤯
-
@cliffordheath @knack @a_mi @hailey I've seen some of your work in this area @cliffordheath and it's mind blowing (in a good way).
A challenge I repeatedly run into is organisations who literally do not care about correctness. Not just "we'll gradually work towards it as budget permits" but literally do not see why it's important to correctly model their business domain in their own software 🤯
@duncan_bayne @knack @a_mi @hailey if your team doesn't even have an unambiguous way of stating the things that you believe to be the case, then not only are you failing to find what is correct, but you remove the possibility of even being wrong. And perhaps that's what makes it so attractive. The broad and shallow path to hell, as it were
-
R relay@relay.infosec.exchange shared this topic
