Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "dev sin"
My worst dev sin is not throwing people under the bus, even when they deserve it.
Literally or metaphorically? I'll leave that up to the imagination.
I believe my second-worst sin is my tendency towards perfectionism. It's hard to finish projects quickly if everything has to be nearly perfect. I still make deadlines, but this is due to overworking, thus leading to burnout.
I could relax more if only I sacrificed my principles...5
Add no comments or documentations whatsoever during my initial years of coding (when actually I used to write code worse than a constipated elephant's shit).. In my mind I would be like "This is quite clear-cut.. A first grader will be able to understand this code.."
But then I had to debug my own code barely some 1-2 months later and I figured out the importance of good comments and documentation..3
My worst dev sin was leaving out the 'WHERE' in a SQL update statement on a production database
Set every booking to be owned by the same sales consultant 👀3
Well, my dev sin is...
Basically every project of mine is not commented, is not unit tested and doesn't have any kind of documentation.
But I try to remove my bad habit!1
Greatest dev sin.... oh god there’s been a few over the years.
I guess one of the top 5 would be making an ecommerce platform without unit testing or documentation for the front or backend. 🤫
Mind you it runs smoothly to this day so I was doing something right 😦1
tl;dr - My company makes me pass around code over email. Is this normal?
How we fix bugs at my company.
1. Simulate bug in dev env (ok, cool)
2. Get the required code from svn and make changes locally (so far, so good)
3. Deploy changes in dev env and test (yeah!)
4. Take screenshots of fix in action along with the files you've changed and mail it to the respective leads (really? send code via mail?)
5. Keep changing your fix based on feedback and keep repeating above steps (what!)
6. Once approval mail comes, check-in your code in the svn branch for deployment and testing in the test env (QA team)
My question to you fine folks is, is this normal? Is this how most companies work? Passing around code over e-mail? Where the different versions of your fix are just attachments in emails. Or have I committed a sin by being a part of this heinous act?10
In fact I'm a sinful dev, so that I can't easily decide which one is worst. From indenting with tabs, or using nano instead of vim/emacs, to hardcoding database credentials on server, to many hacks and workarounds I use as actual "fixes" when the deadline is upon me and I've tried all I could. But it always led only to my own regret. For instance, my latest sin was that I prefered Debian over Arch and used proprietary graphic drivers to speed up my new setup. But ended up with a curse from St. Ignucius. (check my last rant)
But my worst sin probably goes to when I was "printf-debugging" some issue for a GSM controller on a raspberry pi. I forgot to remove one little print line and deployed the new "fixed" version. I didn't follow that project after that for like a month or so, when the client posted back the device and said that "it just doesn't work anymore". It seemed that raspbian didn't boot beacause the sd card was curroptted. I dd'ed through the card and I noticed that there are billions of lines of "DEBUG:: reading stream from 192.some.shitty.ip", took almost all over the 32G sdcard. Just as I suddenly remembered the cursed line I just added a month ago, I declared the sd card dead with no hesitation, dunce-commented the line (so the history would remember), implemented a time out for the thread containing it, setup a journald unit for my service and removed the redirection of process output to a log file, found a new sd card and installed everything again, and finally posted back the new "fix" to the client.
Moral: Never comfort yourself for the sins you have commited in the past kids, they certainly will come back to you. And also not to do any io especially write to a file on an SD card with ext fs, in a potentially infinite loop with no timeout.
P.S: I'd posted my last rant just before the new week rant last nigh. I really liked the St. Ignucius meme so decided to create a new one. He's very adorable :)3
My first dev project was making a small 3D engine in GameMaker 7 when I was 14. I had been using gamemaker for two years then but I never got past the "platformer movement and collisions" and "top down movement and collisions"
It was the first thing I made myself without following a tutorial and spend quite a few afternoons at school to ask my Math teacher to explain things like sin cos and tan. Words I saw on the internet but did not understand.1
my worst dev sin:
Commit and go home on a friday not waiting for the build to pass.
Tons of notification from counterparts the following monday1
Hmmmm my dev sin is probably that when i write some code i neber comment it and dont do even a fucking documentation on it at all.
When I started at my company I was full of energy and wanted to improve the whole codebase. After years of getting blocked by new projects with deadlines month short of the actual time required and missing a lot or all important bits (texts, images. you name it, it's missing) I kind of have up.
I do refractoring now and then but it's not as extensive.
My biggest sin was a nested for-loop that I came across (50+ times nested, previous dev really loved c+p).
I looked at it and started to write the recursive function but stopped half way through, fixed that one error I'm the loop somewhere around 30 levels down, committed and made myself a coffee.
I hate myself to this day for giving up.
Shit I'll just factor that loop tomorrow3
Due to lack of time, I named all the variables in my project without logic,
Like temp1,str1, function dojson etc
Lord be with the dev who's gonna work on that project
PS I am not a bad person, it is the time that made do such things
Dev sin: when you're too lazy to configure ufw (uncomplicated firewall) so you just shut it down instead 😓
I might have just git-committed the cardinal developer sin: not multiplying estimates by 3. Torvalds help me!
So a php app I developed a few months ago when I was first starting as a dev needs an upgrade. Pretty simple since I've known about said upgrade for a while, but the feature was never needed until today.
Told my boss it would take a day or two of refactoring and additions for it to work.
How screwed am I?4
Worst dev sin?
Storing all my personal repositories on a luks encrypted persistent live USB and losing the latest commits of everything because the drive got corrupted.
No backups. Aww yeah 😎.
My biggest dev sin is premature optimization. I'll try to produce the best possible code without the need for it to be there. I will waste my time thinking of wierd edge cases that can be handled with a simple if-else, but why not tweak the algo to handle them internally.
As my first dev job, I took over role of solo programmer maintaining all kinds of custom-made software used by local ISP. It was about 10 years ago.
My first question was where can I find test environment and repo. Apparently there was none and I should learn and develop on production.
My sin was to quickly give up on setting up both test and repo.
My second sin was to continue using the same copy&paste PHTML with register_globals enabled, building over it without attempting to refactor it with templates. I did not use globals in any new code at least.
And I suppose my third sin was that I was playing games when I was done with my tasks. I could have used that time to refactor a bit.
But I think in the end I was absolved from them since I was the only one suffering from this. I stayed with company until it got sold and helped migrate data over (along with myself).
From the day I was born,
Till the day I'll die!!
Every action that I perform,
Is a party if my sin!!
This may not be story of a Dev,
But this is the story of mine!!
I personally don't have a funny dev sin story (not that I didn't commit any).
My internship colleague should update a value of a row in production. So he wrote a SQL command and forgot the where clause. This was the first time the company tested there rollback mechanism and it didn't work. For the next 2 weeks my colleague was busy updating 2000ish rows to make it work again
My dev sin is eating too much at spoons and feeling too bloated to concentrate at work for the afternoon
I have been wondering about this for the whole week, but I don't remember any dev sin... or I don't want to remember it1
My biggest dev sin in my rather short dev live would be my telegram bot written in node.js without any knowledge about JS. Running for almost 1 year without any error handling - oh I almost forgot I haven't documented the code - but the bot is open source, although I haven't worked on it in months1
Worst dev sin? Perpetuating the assumption that we'll build your site for free.
In my defense, my portfolio was lacking.1
Bonus semi dev related sin:
Unless it's piping hot I'll leave my coffee to get cold and then drink it.
My worst dev sin, I feel, is using TurboC++ even now in 2017, the graphics.h file is just too interesting.