Despite the obvious levity, this is actually serious. It was made by why the lucky stiff, a pretty prominent member of Ruby community, back in the day. This, however, was part of his mysterious burnout manifesto, for lack of better term. He really really bloody needed a break.
"programming is rather thankless. u see your works become replaced by superior ones in a year. unable to run at all in a few more."
20 Comments
Toes@ani.social · 41 pts · 2y
Where does maintaining a 25MB perl script fall into.
JohnWorks@sh.itjust.works · 30 pts · 2y
camr_on@lemmy.world · 22 pts · 2y
My condolences
InnerScientist@lemmy.world · 17 pts · 2y
EOL
PlexSheep@infosec.pub · 13 pts · 2y
I think that's larger than my kernel binary.
nxdefiant@startrek.website · 13 pts · 2y
💀
Kerb@discuss.tchncs.de · 5 pts · 2y
into depression i guess
SpaceNoodle@lemmy.world · 26 pts · 2y
Documentation should be larger than code.
Tests as well.
umbraroze@lemmy.world · 11 pts · 2y
In most programming languages, yes.
In Ruby? ...eeeeeeeehhhhhhhhh.
SpaceNoodle@lemmy.world · 7 pts · 2y
Programming, not Ruby.
xmunk@sh.itjust.works · 20 pts · 2y
Where does "Suddenly realizing why they call it DLL hell" fall on the scale?
nyan@lemmy.cafe · 4 pts · 2y
Between "One too many nulls" and "The tests are larger . . ." in the beginning, then moving up one notch for each day you've been wrestling with it.
redcalcium@lemmy.institute · 17 pts · 2y
The purpose of the code is to make the tests pass.
ChaoticNeutralCzech@feddit.de · 8 pts · 2y
The purpose of code is to solve a problem but don't tell that to the newbies or they reduce the PHP codebase you spend full time managing to 10% that in Rust and take your job.
tyler@programming.dev · 10 pts · 2y
I miss why... he was what everyone really needed, and the industry destroyed him. I haven't seen anyone like him since.
nullPointer@programming.dev · 9 pts · 2y
50,000? thems rookie numbers.
Sylvartas@lemmy.world · 1 pts · 2y
laughs in unreal engine
asyncrosaurus@programming.dev · 5 pts · 2y
Is such a weird complaint. You should aim for your codebase to be as small, simple and readable as possible, while your tests should be a specification that guarantees behavior is consistent between refactors. When you add behavior, you add tests, when you remove a behavior, you delete tests.
The size of either is independent of eachother. Small code bases that provide lots of features should be simple to read, but with a lot of tests.
Celofyz@lemmy.world · 4 pts · 2y
I always tought that it's a norm to have more code in tests than in tested program
CaptPretentious@lemmy.world · 1 pts · 2y
I was building up some packer stuff. Vsphere-iso plug-in. Tests were going fine and then for reasons I didn't understand it said it could no longer find the cd creation tool it has just been using.
So I try a few things, nothing works. So I figure I have nothing to lose, I make a new folder to house all the tools in one place. Update Windows system environment path. Restart everything. VScode didn't have my path statement, Google is of 0 fucking help, and now packer doesn't work. I least it's the weekend now.