←back to thread

Development speed is not a bottleneck

(pawelbrodzinski.substack.com)
191 points flail | 2 comments | 05 Sep 25 13:13 UTC | HN request time: 0.001s | source
Show context
HumblyTossed ◴[05 Sep 25 13:51 UTC] No.45138581[source]▶
You have the unbelievably productive programmers - we all know their names, we use the code they wrote every day. Then you have the programmers who want to be there and will try everything they can to be there - except gain depth of knowledge. They tend to be shallow programmers. If you give them a task and spell it out, they can knock out code for it at a really good pace and wow upper management. But they will always lack the ability to take a task not spelled out and complete it. Vibe-coding is like sugar and crack mixed together for these people.
replies(3): >>45138811 #>>45139628 #>>45147339 #
throwaway-18 ◴[05 Sep 25 14:10 UTC] No.45138811[source]▶
The difference between Software Engineers (or Developers) vs Programmers; with the latter designation being a stretch for some.
replies(1): >>45139688 #
1. hombre_fatal ◴[05 Sep 25 15:27 UTC] No.45139688[source]▶
I think we should we put this title-based distinction to rest.

Whether you call yourself an engineer, developer, programmer, or even a coder is mostly a localized thing, not an evaluation of expertise.

We're confusing everyone when we pretend a title reflects how good we are at the craft, especially titles we already use to refer to ourselves without judgement. At least use script kiddie or something.

replies(1): >>45140483 #
2. bob1029 ◴[05 Sep 25 16:33 UTC] No.45140483[source]▶
In my local world: Writing code to specification is programming. Writing the specification is engineering.