Stripe's take on software engineer efficiency made me angry
threadreaderapp.com
Stripe's take on software engineer efficiency made me angry
1–10 of 15 posts
Re: Stripe's take on software engineer efficiency made me angry
#2After a while, I can guess where bad code comes from. Code that is hastily written by someone experienced is very different than code assembled by the inexperienced and without good guidance. Feature creep also has an obvious quality. Trying to turn these things into simple metrics is very much a mistake.
Re: Stripe's take on software engineer efficiency made me angry
#3After a while, I can guess where bad code comes from. Code that is hastily written by someone experienced is very different than code assembled by the inexperienced and without good guidance. Feature creep also has an obvious quality. Trying to turn these things into simple metrics is very much a mistake.
Yeah but there’s money to be had from people who will buy into that idea. People don’t like complex answers.
Re: Stripe's take on software engineer efficiency made me angry
#4It says something about the state of software development in the 21st century that I thought it was pretty brave of the author to put his actual name to that. (And FWIW, I absolutely agree).
Re: Stripe's take on software engineer efficiency made me angry
#5After the landing page I didn't even went ahead and read the report because I dismissed it as content marketing. You can see the entire thing is targeted at managers not at software engineers.
Re: Stripe's take on software engineer efficiency made me angry
#6Software creation (is it really 'engineering'?) lives in the penumbra between arts and science. This leaves it open to interpretations and conjectures from various points of view. The definitive assessment has yet to be made.
Re: Stripe's take on software engineer efficiency made me angry
#7Software creation (is it really 'engineering'?) lives in the penumbra between arts and science. This leaves it open to interpretations and conjectures from various points of view. The definitive assessment has yet to be made.
This is where we revive the debate about whether programming can be creative because it follows such rigid syntax rules. The unenlightened say it's not, and the obsessed say it is. How do we communicate across this gap?
Re: Stripe's take on software engineer efficiency made me angry
#8Software creation (is it really 'engineering'?) lives in the penumbra between arts and science. This leaves it open to interpretations and conjectures from various points of view. The definitive assessment has yet to be made.
This is where we revive the debate about whether programming can be creative because it follows such rigid syntax rules. The unenlightened say it's not, and the obsessed say it is. How do we communicate across this gap?
Programming languages having rigid syntax is like English being limited to the Latin alphabet - the opportunities for creativity lie in the combinations of higher level structures.
Re: Stripe's take on software engineer efficiency made me angry
#9Great article. I totally agree, but I see alot of Stripe developers seem to forget that 99% of software is maintained in large companies and outside of their "startup" mindset where code doesn't always live that long
Re: Stripe's take on software engineer efficiency made me angry
#10Software creation (is it really 'engineering'?) lives in the penumbra between arts and science. This leaves it open to interpretations and conjectures from various points of view. The definitive assessment has yet to be made.
This is where we revive the debate about whether programming can be creative because it follows such rigid syntax rules. The unenlightened say it's not, and the obsessed say it is. How do we communicate across this gap?
Can we agree that sonnets are uncreative and that heroic couplets are?