News for hackers. Stuff that matters.
Re:The Coming Knowledge-Work Supply-Chain Crisis by ozim on Monday April 28, 2025 @01:12AM (#43817785)
My observation over the years as a software dev was that velocity is overrated.

Mostly because all kinds of systems are made for humans - even if we as a dev team were able to pump out features we got pushed back. Exactly because users had to be trained, users would have to be migrated all kinds of things would have to be documented and accounted for that were tangential to main goals.

So bottleneck is a feature not a bug. I can see how we should optimize away documentation and tangential stuff so it would happen automatically but not the main job where it needs more thought anyway.

Re:The Coming Knowledge-Work Supply-Chain Crisis by charlie0 on Monday April 28, 2025 @01:18AM (#43817818)
This is my observation as well, especially in startups. So much spaghetti thrown at walls and that pressure falls in devs to have higher velocity when it should fall on product, sales, exec to actually make better decisions.
Re:The Coming Knowledge-Work Supply-Chain Crisis by jaimebuelta on Monday April 28, 2025 @07:50AM (#43820297)
Good iteration process is really important. Just throwing things faster into the wall doesn't help if you don't pause to check which one sticks, or, even worst, you are not even able to know which one sticks.

That's a very human reflective process that requires time.

Re:The Coming Knowledge-Work Supply-Chain Crisis by ebiester on Monday April 28, 2025 @10:56AM (#43822192)
I'm really working hard to figure out how to optimize away documentation, but it's seemingly harder than writing the code. It's easier to generate the code from the documentation than the documentation from the code, reference documentation (like OpenAPI docs) aside.