←back to thread

Senior Developer Skills in the AI Age

(manuel.kiessling.net)
421 points briankelly | 7 comments | 03 Apr 25 18:47 UTC | HN request time: 0s | source | bottom
Show context
Quarrelsome ◴[03 Apr 25 21:09 UTC] No.43575443[source]▶
This is extremely fascinating and finally something that feels extremely tangible as opposed to vibes based ideas around how AI will "take everyone's jobs" while failing to fill in the gaps between. This feels extremely gap filling.

I find it quite interesting how we can do a very large chunk of the work up front in design, in order to automate the rest of the work. Its almost as if waterfall was the better pattern all along, but we just lacked the tools at that time to make it work out.

replies(2): >>43575549 #>>43577333 #
1. skizm ◴[03 Apr 25 21:17 UTC] No.43575549[source]▶
Waterfall has always been the best model as long as specs are frozen, which is never the case.
replies(4): >>43575820 #>>43575873 #>>43579828 #>>43580347 #
2. Quarrelsome ◴[03 Apr 25 21:42 UTC] No.43575820[source]▶
sure, but if you're generating the code in a very small amount of time from the specs then suddenly its no longer the code that is the source, its the specs.

That's what waterfall always wanted to be and it failed because writing the code usually took a lot longer than writing the specs, but now perhaps, that is no longer the case.

replies(1): >>43581527 #
3. thisdougb ◴[03 Apr 25 21:48 UTC] No.43575873[source]▶
When I first started in dev, on a Unix OS, we did 'waterfall' (though we just called it releasing software, thirty years ago). We did a a major release every year, minor releases every three months, and patches as and when. All this software was sent to customers on mag tapes, by courier. Minor releases were generally new features.

Definitely times were different back then. But we did release software often, and it tended to be better quality than now (because we couldn't just fix-forward). I've been in plenty of Agile companies whose software moves slower than the old days. Too much haste, not enough speed.

Specs were never frozen with waterfall.

replies(1): >>43577158 #
4. PaulDavisThe1st ◴[04 Apr 25 00:40 UTC] No.43577158[source]▶
The difference between agile and waterfall only really matters at the start of a project. Once it is deployed/released/in-use, the two approaches converge, more or less.
5. zelphirkalt ◴[04 Apr 25 09:03 UTC] No.43579828[source]▶
Many companies now engage in serial waterfalling.
6. kristiandupont ◴[04 Apr 25 10:36 UTC] No.43580347[source]▶
Only if you don't learn anything while developing. Which is also never the case.
7. datadrivenangel ◴[04 Apr 25 12:50 UTC] No.43581527[source]▶
Specs aren't done until the product is retired, thus, code ain't done either.