Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
My worst developer sin is probably me talking sh*t about programs I could never have done better myself.
"Omg, this is so inefficent!"
"Omg, the ui is so confusing!"
"What kind of idiot would do that?"
...I'm not the only one who does that, am I?10 -
Adding some scripts to a project with the whole intent of slowing performance on Internet Explorer, and if a client complained I showed them how fast it was on Firefox, Chrome or Opera.15
-
Mistyping one character wrong in a password and hitting backspace until I am sure I’ve deleted the entire Wikipedia.
Then starting all over again.3 -
Begin a lazy fuck -> not taking the time to learn git while I've had plenty of time and now I still hardly know how to use it.17
-
I'm distracted easily. I sometimes take up to 4-5 days to finish a task that would've taken a-productive-me just a few hours to complete.
All this tech and all those interesting strangers on the internet...damn.
19 -
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 -
Sometime around 2010 a colleague asked me to join him in developing mining rigs for some shit called “bitcoin”. I thought it was dumb as hell.
He’s a millionaire now.2 -
enabling firewall on a vps to secure my docker containers and forgetting to add openssh to allowed list --> ssh blocked 😃🔫24
-
#1
Thinking Edge might actually be the next new browser.
And then using it for a few weeks.
#2
Not documenting my code 😥6 -
Please don't kill me!!
I started using dark theme in all IDE I use just today.. all those years I was using Light theme !9 -
Well, maybe a year ago when I tried to learn JavaScript, I named my dir "Java" just because I wanted to shorten JavaScript -_- when it saw my dev classmate he was laughing af and he still reminds me that7
-
Client calls: "hey man, my shit isnt working".
Me: "uh... Have you pressed ctrl+f5?" while coding on the speed of light so i can say it was his browser problem -
I was learning about packets and I was trying pirni (like Wireshark for iPhone) on my local network. I found a packet of my my roommate about a recipe of fancy a fancy dish
me: *enters the kitchen* Bro you need to see this I got this sick recipe of $fancyDish that I really wanna try
le roommate: THERES NO WAY ARE YOU FREAKING KINDING
I know its wrong to spy on peoples trafic but it was worth it hahaha7 -
Sent HTML to google translate server side to support multiple languages.. actually worked pretty well but it made me feel dirty for weeks.1
-
I accepted a job that requires coding in html, css, js and php and I don't code in those languages at all. Whoops.8
-
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 -
DON'T SUDO WHEN DRUNK
I rm-rf'ed my linux vm when i was drunk, and darn, it was wiped, clean and fresh12 -
"It's just a tiny change in one function. What can go wrong? I don't need to test, I'm not that stupid to mess this up". Apparently I am. Pushed the changes, and the [Firefox] extension basically stopped working. Lost about 1.5k users in 2 days. Good times ;)2
-
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 👀2 -
My worst devSin was testing in production once because I was too lazy to set up the dev environment locally.
Never will I do that mistake again!4 -
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 -
Only starting to use Linux (mint) as main os a month ago
Penguin fact: the largest living penguin species is the emperor penguin (1.1m tall, weighs 35kg)6 -
I spent three hours making a custom color scheme for my instance of visual studio. Almost every color in it is a variation on hot pink. I've used it every day for the last three years.
The background is black, though, because I'm not a complete animal.8 -
Put random text in window.alert() where ever I got error in JavaScript code. Random text like 1) If you see this, you are fucked; 2) error 001; 3)why today; 4) the code is breaking here etc.
And never removed them. They are the running in production till now. I am just thankful to the gods that the code Nevers break and the user does not get browser alert and also the fact that I don't work there anymore.4 -
#include "somefile.c"
My teacher: "Including a .c file instead a .h header is a mortal sin."
This was long ago, so I believe gcc has already forgiven me.2 -
Greatest dev sin.... oh god there’s been a few over the years.
Hmm 🤔
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 -
— Filezilla *open prod ftp*
— right click a file *edit*
— edit the file, save,
— filezilla *save new file*1 -
I hardcoded credentials into source code because I was too lazy to write the method to read them from the database properly.1
-
Using pokemon exeption handling on some very important and sensitive back end stuff to meet a deadline.7
-
Giving up/panicking/talking myself down when shit gets difficult ;/.
I always want stuff to work immediately, and I hate it when I don't understand something.
But since this is such a big part of working in dev, I should learn to keep going!2 -
I worked about two years on a browser game without using any version control. I also thought it would be nice to have absolutely no comments in the code.
-
Biggest sin is writing code without taking into account clean coding and just doing what ever is necessary to make the code work6
-
Amending ancient Git commit messages because there's a typo and then force pushing
RIP everyone else working on the same project2 -
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 :)
1 -
Why you should always backup.
Nearly a year ago I developed a whole project (iOS, tvOS, watchOS), but I never backed it up because I had a recent machine and thought the chance that something happens to the disk is so small I didn’t backup. But then my mac didn’t start correctly. So I needed to reset it. Lose the project, some other files but not much else. Then I recoded the project and backed it up on multiple places. But a little later, I was writing another app, again didn’t copy again... This time I deleted the wrong folder and deleted the trash, was gone too. So from then I learned to copy everything I coded. All projects I work on, I keep a copy of on an external disk, GitHub and Bitbucket. Assuming they wont crash all at the same time 😉.
So I recommend everyone to backup all your code. Even if it’s only 500 lines. Losing it is hard...3 -
Sins? I don't want to keep you up all night, so here are some highlights.
Fucking with clients and employers who fuck with me first, or waste my time.
Occasionally not documenting my code (I'm actually pretty good about this), then bitching about poorly documented code.
Honestly wishing other people in the office would *actually* explode, or die engulfed in flames.
Working drunk and/or stoned.
Getting pissed off when I have to do something in a stupid way, or use a workflow that I don't like.
Seriously fucking up out of either arrogance or stupidity, then blaming it on something else.
Zoning out, skipping work, or sleeping in and billing for it (see sin #1).
But my greatest sin? That honor's got to go to becoming a developer in the first place.
I wasn't always a professional asshole, but I fucking am now.1 -
It was at the beginning of my IT apprenticeship, I had no idea about coding in C and our teacher told us to write a "hello world" in C.
.. I wrote:
10 PRINT "HELLO WORLD"
20 GOTO 101 -
Even though I bragging about how good my few projects are to the people I talk to them about, I undervalue my worth as a developer.
Even though I am desperate for money, I've only recently started trying to get work in the dev community (with little success) because I actually feel that I'm not a good enough developer..17 -
There are always guys coming with the same million dollar app idea every few weeks that want me to develop the app for share of the future revenues.
Btw the idea is always like this: "he man, i got an app idea which will make us rich quick. It's like Facebook and Instagram mix but with tinder functionality."
7 -
I saved passwords to db hashed to SHA-1 with no salt... I left that company but I'm sure that application is still actively used today.2
-
Ugh all but one unit test is passing :-(. I know the code is working- so the problem must be in the test... [add @ignore to test]. Yay they all pass now!1
-
"'This is just a temporary fix, I'll refactor it into something great and modular later" thought I as I continued to sin for the umpteenth time.
-
I once made a pull request fully aware that 3 tests were failing. The PR was approved and merged.
In my defense, they were very complicated tests and I fixed them a few days after.2 -
TLDR I messed up my partitions!
I had on old netbook with Windows on it, it was getting painfully slow. So I thought, why not try dual boot?
Since I had never installed a GNU/Linux OS before, I messed up the partition. Like, really, really badly.
Somehow, i accidentally created like a 100 1kb partitions. Windows wouldn't boot, no other OS was present. Shit had started to hit the fan.
Turns out there was this easeUS partition manager, that you could make a bootable USB with it. So I did that, deleted all partitions, created new one, installed Linux Mint on it. I've done a lot of other shit like this, but this rant is getting too damn long. -
I've spent the last day at work playing Paperclips 📎. I fucking hate the author of that time eating machine!
-
Don't test complex functionality before production.. neither unit, nor system tests involved for my android app. Releaseing solely based on hope!2
-
Not learning unit testing... I've heard so many good things about them, but I've never learned how to inple.e t and use them.
Maybe I can start now, can anyone point me in the write direction?4 -
A few years ago, i was kinda bored on my internship, so i changed the name of all variables of some jquery functions i had on my code with lyrics from a song that was stuck on my head.
Never understood that code again.3 -
My physics teacher would call it a sin. Technically enough for wk81 xD
Yeah, i coded an entire NN on paper while physics lesson. Worked pretty well. Except it doesnt work yet :/ Compiler errors because of some referenncing issues1 -
1.
Never programmed something useful because i have no ideas...
2.
Never used comments in my projects6 -
I'm all about concepts. I start some project, go through solving major problems, and test it just to scream "It's alive! It can be done, an works!"
Then I lose interest and move on to something else...1 -
Editing java files on server for deployment.
Deployed. Found major issue.
Don't have time. Editing source code on server changed if else
Rebuild and deploy.
Now push from server to repo and pull locally...
Pure sin. -
Client calls me requesting a new simple feature.
Connect to FTP server.
Edit some PHP pages and upload them back, check if the changes actually worked.
Basically implementing and testing a new feature on a live production website...
PS. It didn't work the first or second time -
Sometimes for personal projects (and one client gig) I use the same database for local development and production.
Why?
Because I am a piece of shit.6 -
Complaining about people not understanding basic python syntax but I also don't know even know how to use fucking scratch.2
-
git commit -am 'needs refactor'
// months go by
git commit -am 'hotfix, also needs refactor'
// ... repeat -
- i = ++i or i = i+=1
- No Documentation
- Not Splitting up a Stylesheet
- function()
{ }
if(){ } (inconsistent style)
- Using a ton of if's instead of a switch
- Installing Nvidia drivers manually on Linux thrice! Had to reinstall it everytime!
- sudo rm -rf /
- Being unorganized in terms of personal projects.1 -
So… I prefer nano over other terminal editors (Mainly because I don’t understand how to use others properly) and I wasn’t really aware of the VISUAL and EDITOR environment variables. So on my Arch machine most things would default to vi. Vi to me is like an annoying pop-up that really doesn’t want you to close it (Tho, one thing I did learn eventually was how to close it ). So at some point I quickly wanted to edit crontab as root and I just couldn't manage to get crontab to use nano. So what did I do?
sudo pacman -R vi
ln -s /usr/bin/nano /usr/bin/vi
I symlinked nano to vi and it finally worked. I know that there are probably countless ways this could’ve been done better but in that case I wouldn't have posted it here under wk81 ;)5 -
I (tried to) use GitHub to version control one of my websites, and doing a pull on the web server broke the entire thing.4
-
I'm still performing the sin that got me into my first real programming language:
Bukkit Plugins ...13 -
I haven't turned off my work laptop since over a month. I restart occasionally when Windows update demads it.
I have TeamViewer running in this and since workplace has 24/7 electricity and highspeed internet, i use it if i have to download something huge and important.
In addition to that, I'm using it for something else, which will get me fired if found out.
Believe it or not, nobody has yet noticed since last 6 months that I leave my system running 😂8 -
Biggest sin? Easy. Pushed directly to master branch and deployed to prod. I should mention it was something very small before I get crucified😂
-
Tight deadline, codebase not mine, I wrote an hack that read a dom element in the page in js extract some data, append it to the query string and then refresh the page to get the desired result. All the rest of the logic is in PHP. I still feel guilty.
-
Biggest sin
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 -
Not actually solving the problem in an error and instead implementing a workaround thinking "no one's going to read this code anyway" when I'm actually just condemning my future self to a lot of hell.1
-
I sometimes wrote song lyrics in comment format on my code while i listen to the music, so my boss will think that i actually write some badass lines of codes.
-
Mine: not listening to early warning sings that shit won't work. As a result we implemented the wrong technology and had to roll back after a month in production. Lost some customers data, though we had backups, so it was just a delta of a day or so. Still, not pretty, had a rough night writing scripts at 3am to check data validity after.
I will throw in another one from a colleague of mine. He was running some database migrations and ended up pointing the DB migration tool to production by accident. Oops. That one required a restore as well, if I remember correctly. -
Doubting my decision more than I should even though they're right, thinking too much about it and eventually making wrong decision.1
-
Today, I had a small, but funny conversation with a person I knew from my education (application developing).
He suddenly asked, how to prevent using HTML-Tags in PHP.
So I send ihm following line:
$string = str_replace(array("<", ">"), array("<", ">"), $string);
Shortly after the line, he asked, how to add this into his query, which looks like:
$query = "INSERT INTO comments (name, email, quote, hinzugefuegt, ip_adress) VALUES ('" . $_POST['vName'] . "', '" . $_POST['eMail'] . "', '" . $_POST['q17'] . "', NOW(), '" . $_SERVER['REMOTE_ADDR'] . "')";
Now I thought: "Well, he don't even secure his variables", and I posted a Pastebin, which only "fixes" his issue with replacing the HTML-Tags, but still allows SQL injection.
https://pastebin.com/kfXGje4h
Maybe I'm a bad person, but he doesn't deserve it otherwise, because when I was still in education with him, I told him, he should learn to use prepared statements.3 -
When I was starting programming (learning Actionscript 3) loong time ago I for some reason didnt stubbornly write code into .as files... Instead I just attached code to timeline keyframes in Flash...6
-
Sometimes I commit fixes for issues on my crypto exchange api repos without testing them and tell the issue author to test it themselves because "I don't have api keys for the respective api" to test it.
I'm fully registered on every exchange from here to Japan. 🙄 -
The few times i have pushed code to the repo when it's not ready.
Granted it was so i can carry on working on it elsewhere but it wasn't my proudest moment.4 -
I once nuked a Ubuntu os by trying to upgrade the systems python version beyond 2.6...I now use virtualenvs.2
-
My biggest sin is overshooting the problem - developing something "with the future in mind" which ends up way more complicated than it should be.
It works, works great, but nobody can maintain it because of the complexity, and because I usually write no comments in these situations.
But hey! At least I'm aware of it and working on fixing it in me.3 -
Blaming the computer when in reality you commented out about 80% of the code (by accident), and not noticing for a good hour.
-
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.
-
Including jQuery everywhere even if the size of my code is lesser than size of the plug-in itself.1
-
Forgive me Linus for I have sinned. It has been since the dawn of time since my last confession.
I hardcoded naming conventions for file names into a script that is used to remove incorrect lines of text that are created during our process to create the files that we send out so that healthcare claims get paid correctly and copy and pasted the code for each new state’s health plan since the users(who are supposed to be technically inclined as they’re in IT as support analysts) can barely figure out how to set up the excel file to remove the lines. There are now 18 files of the same python script with different US States’ names.2 -
(When L1 support fails to investigate before routing to L2)
User: I couldn’t able to view my files saved in network drive
Me: we have checked files on sever side its visible and u have access as well
User: my screen has broken so I couldn’t able to see
Rest is history1 -
Telling family and friends "I'll develop your site but it'll take a week" when I really mean "I'll spend 45 minutes on a visual builder for WordPress on my way home on Friday"2
-
I use version control as a glorified backup. Only recently did we start branching at work.
This is why I need to be part of a proper team where I can learn instead of being a team of 2 juniors and no one else 😂 -
In Java, I use dummy variables to set breakpoints and get around the return unreachable compiler/Eclipse check2
-
I had to make a project for university with a colleague and we shared code through google drive because none of us never used git.
Don't insult me too much please 😂 -
I love Microsoft softwares and Apple hardware but I try to keep them away from me to prefer free softwares or at least MIT license things.
That's something that makes me feel guilty.4 -
I've never written any unit tests for any apps/programs I've developed.
I would tell myself, this time you're going to create some and be a better developer by doing so. I end up just creating the file and that's it.
Most of the bugs are discovered during the user testing phase so I always end up being lazy writing unit tests.
I write very defensive code though so that helps a little but all in all, it's a very bad habit that I need to snap out of4 -
Deployed an hotfix without going through QA. Not the worst, but against what I like to do.
And there was time, a long time ago, when tests were a luxury... I know stupidity at its purest 😅1 -
Right now I just found out that I forgot the basics, but still able to do some complicated shit
Brain fart 🧠 💨1 -
Today I made a php script to scrap a site.
And I needed to use str_replace in a string to cancel out some values.
Instead of doing simple str_replace I used explode func to separate them with spaces (without any comments on how or why the fuck I m using an explode instead of a str_replace).
Later, I used $p[1] for further processing.
-
My biggest regret is getting into a project and not finishing it. I Almost feel like I should force myself to finish up these project before I start new one.
-
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 have a really hard time staying focused reading through legacy code. As a result, I often miss many subtle details about how a given system is currently functioning.
-
When you develop a standalone page using JS and the old JS, JQuery libraries interfere with your current libraries!
Delete
Delete
Delete
..
.
..
Open that js file rename
Open that min.js file rename
..
.
..
Still Not working!
Cleared cache ... works like a charm!
Damn you cache and min.js!!! -
Sins? All of em'.
Infinite loops of recursive callback carnage, just because I like to watch it burn. -
I don't save computer resources... I mean come on, there is a hundreds of gb RAM, dosens of cores, who cares if code has some line more if it's more easy to read...2
-
My biggest ongoing sin is that I neglect commenting while maintaining a legacy system. No one else has commented anything so why should I? Well I should. I comfort my self with the fact that this legacy system will be replaced with a shiny new well commented one in the near future, which im also working on.
-
confessions[0]
I got into hell and sinned there.
This was a few years back when I was getting into webdeb. I was working with WordPress at that time and a start-up asked me to help them build a website on WordPress through a mutal friend. That was my first WP site and it is a jungle of unorganized code. I didn't bother making a child theme, overwrote PHP files without documenting it and changed CSS in the orginal files. Instead of a child theme, I made a monster.
The worst part is, that site has never seen an update coz an update in WordPress would undo all my work. I should prolly burn the server the site is hosted on to purge my sins. -
I run auto-formatter with every typo correction so nobody notices. 300 lines changed, message "formatting"
-
That time the Saturday before last when I wasn’t paying full attention to which environment I was in and I accidentally deleted an entire hosting account and had to re-create it from a backup. First, only, and hopefully last time I ever do that.
-
Building apps in angularjs and Clojurescript and Om
But can't understand how to migrate to react from angularjs and how to write react.
Which is funny as Om is React based -
This is a group sin.
We'd get the code checked and then run it straight to live. No test environments no real back up in place or process for releasing.
Just run code in if it broke run fix 1 through 3 until you got it right. That was two years ago. -
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 -
Not purging my senior devs code from missing curly branches earlier. Maybe not my worst sin, but DAMN DO I REGRET IT NOW.
-
My dev sin is eating too much at spoons and feeling too bloated to concentrate at work for the afternoon
-
Not working side projects enough. Really puts me behind where I could be but working 9-7 5 days a week I really CBA in my spare time.1
-
lol every time I look at actively maintained code on GitHub
Thing is, there'll always be things I don't know. One needs to learn that. However, it's not an excuse to stop learning, so just keep learning every day and be confident in what you know -
confessions[1]
I've started way too many projects. Even more than the number of times I've shopped clothes for myself. But I rarely complete anything ever. Once the learning phase is over and I've to actually do the typing out the code part, I lose interest and leave the project and start new ones. -
Blogging / writing, helps to think of something else to be able to solve dev problem.
And sleep (know if you're a morning person or not and know with that). -
Not learning to unit test as I was embarrassed that'd I'd missed it in college.
Now, thanks to a great ruby module I've taken this year, I'm leaning towards TDD. I really enjoy it. -
Worst sin ever was during a workplace hackathon.
Being ultra competitive I decided the other teams build script was too functional, ie. It worked. Changing it to
.echo please accept our warmest contrafibularitiea and have a nice day
...and commit gained more than a little (deserved) approbrium. -
Me, taking a coding class in uni:
Purposely cramping everything in as few lines as possible, making the code barely readable, just to screw with the guy who had to correct this mess.
In my defence, the assignment they gave us was garbage. The task descriptions were often ambiguous or even contradictory to what actually was the case ("The InputStream will contain a string of csv data, each element starts in the next line" -> was a malformed single line string) and the automated tests they wrote to check our output where either completely unhelpful because of their meaningless error messages, or sometimes even plain wrong, telling us our output was wrong, even though it definitely wasn't. -
Was feeling over-confident one day, wrote a delete query and pushed to production without double checking it.
Turns out the where clause always returned true and deleted all rows in the production table.
Mind you, from that day onwards I'm using update queries instead of delete.. -
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
-
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 it
-
A few years ago, while in college, a friend and I were working on a engine as a side project to build experience. 25% of the goals completed and he begins making excuses to not work anymore. I continues working on it and when the project was "competed", I showed it to the head of the department at the college where I was offered a job as a professor and sold the engine for 20k to the department of engineering.
The dude came back claiming recognition and compensation for his effort I told him sure.
When we met, I showed him legal paper stating the engine was patented under my name and I was the only owner.
In reality, I wanted to meet with him to breath his ass then show him the paper but I felt that would be too evil.
I was pretty mad that he came back after leaving but I can't hold good for nothing people. -
Where to begin?
- I purposely overestimate because I can get away with it in current job
- I test in production like 50% of time in current job
- I deploy during working hours
- My javascript is a sphagetti monster in current intranet implementation and I am sorry for the next future maintainer after I'm gone...1 -
Having such bad ADD that I have 20 different projects going in 20 different stacks / languages.
It's cool to have breadth but now I really need depth. But what do I choose?
Ah fuckit I'll just go try out this other shiny new thing. -
I often get distracted by other incompetent teams and preach ddd and tdd to them instead of writing my own code1
-
For me it's definitely teaching. Whether I teach coding or any mathematical or even theoretical subjects. I find that when you teach someone you learn how to communicate better and transfer knowledge effectively. Communication is key in client relationships.
Secondly when you teach someone a concept you think you understand you tend to find flaws in the way you understand that subject matter by forcing you to hear your explanation out loud. This in turn will make you delve deeper into that subject matter and make you understand it better, rearranging your own perceptions and correcting those flaws. -
Modified stuff on production server without checking documentation, because I was cocky and tought that I remembered everything. The worst thing is, that right after that I took a lunch break and only realised what have I done after that. For an hour or so anyone who opened our app experienced an instant crash...
-
Knowing that QAs hate broad impact analyses, must test every path, yet love someone else writing their test plans, "everything is impacted. You need to test it all".
-
worst sin? 🤔
I guess not following any best practices, really bad formating, no comments, simply puting all code together just to make it work. I cry everytime I have to dig through my old codes 😫 such a shitty code, such a shitty programmer I was (am) 😔😓 -
Estimating a 1 day change as 4 weeks when the scrummaster, product owner & BA haven't bothered to run the simplest dilligence check and can't be arsed to even give a quantitative valuation.1
-
To be honest spent a year of work time on a team of 2 developing a product that 2 people have bought, £1000 revenue... 1 year after release.
At least we didn't waste time writing tests. -
Preaching TDD/TFA without having gotten there quite yet. I have unit tests, but only half are actually TFA :(
-
I took a long time to use prepared statements in a production php application instead of directly constructing the SQL query with the variables I had...
Like $sql = 'SELECT * FROM foo WHERE y = '.$search; -
I'm an undergrad junior android developer who has followed Kotlin ever since it came to light but still haven't written a word in it. I hope the android lords forgive me.
Top Tags
Weekly Rant
View