←back to thread

Senior Developer Skills in the AI Age

(manuel.kiessling.net)
421 points briankelly | 2 comments | 03 Apr 25 18:47 UTC | HN request time: 0s | source
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 #
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 #
1. 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 #
2. 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.