I once had a co-worker (QA guy) who had the worst smelling breath of anyone's I ever smelled. He was a nice guy but it was kind of weird/irritating how bad it smelled. One day someone confronted him about it, and he said that it was garlic since he apparently constantly chewed on garlic. I guess it was just some odd habit and he didn't care he was grossing everyone out haha.

A previous co-worker (dev) bought a "foot mouse" he found on a Chinese website, then changed his keyboard's layout to match the "natural human cognitive ability" also bought a sleeping bag because he needed a "power nap" after lunch break he even asked our MD to buy him an ergonomic chair which would cost around 1200 USD ( of course our MD refused) then the worst of the worst, he had this habit of chewing his food loudly when he's eating something he likes.
One time our operations manager (she was pregnant XD) screamed at him from her desk " RAYAAAAN SHUT YOUR FUCKING MOUTH I CAN HEAR IT FROM HERE DAMN IT"

He literally spilled some of the food he was chewing on his desk and I burst out laughing like crazy.
On the same day our MD told us to follow a new "no food in office" policy 😂😂😂

Sad story is that when he left the company I had to revert his PC to how it was including resetting the keyboard layout to default, remember his "foot mouse" ? Well he had to modify the mouse settings so all directions were inverted.

The first thing I said when I turned on his laptop was

FUCK YOU RAYAN!!

All fun and games until you inherit a legacy c project with 30k+ lines of code and a habit of leaking memory and segfaulting intermittently.

That's my worst nightmare at least.

At one of my former jobs, we devs had to do all sorts of non-dev work, such as writing quotes and even contracts!

The CEO of that company had this naughty habit to contact devs directly without delegating through the CIO. Sure, if it's really urgent like when some system is down because of a bug, go ahead and disturb a dev. But interrupting coders to write some freaking quote? Come on!...

Once, that CEO asked me to stop everything I was doing to write a quote to a customer ASAP, as this was really urgent.

I spent several hours writing that quote. It had to be done right as any specifications in our quotes were used in our agreeements and were referred to in the case of any dispute. So not only were we devs and salesmen in the same time; we also needed to be lawyers.

When I was done and delivered the quote to the CEO, he told me he had no intention to take on that customer in the first place. Instead, he wrote a polite we-are-not-interested e-mail to the customer and cc:d it to me just so that I could read for myself how very sleek a businessman he was.

Me: why did I have to write that quote when you knew all along that you were not going to use it anyway?
Him: It's for your own personal development.

Another naughty habit of that same CEO is that he made "jokes" and remarks that I found inappropriate, such as "You walk like a drunken sailor".

Later, he decided to discontinue our team/product because "it isn't proftable". Well, what do you expect when devs are forced to waste half day completing pointless tasks?!

It was for the better anyway, and I was actually relieved when I left the company. I'm still thinking though, that the real reason he sacked me is that I am too honest and not the docile kind of employee that would be ideal for him. I did question some of my tasks, and worst of all: I didn't laugh at his stupid jokes.

PSA: negate your tests and make sure they fail!

I have what I thought was a weird and slightly paranoid habit. When I write tests sometimes just as a sanity check negate the assertion to make sure the test fails and isn't a false positive. Almost always fails as expected.

But not today! Turns out I had forgotten to wrap my equality check in an assertion so it would always pass. It freaks me out to imagine pushing a test that always passes not just because it doesn't do its job, but could also obscure a bug and trick me into thinking it works differently than it does. Broken tests are the worst!

But it pays to be paranoid.

I'm a student at a cyber education program. They taught us Python sockets two weeks ago. The next day, I went home and learned multithreading.
Then, I realized the potential.
I know a guy1 who knows a guy2 who runs a business and could really use an app I could totally make. And it's a great idea and it's gonna be awesome and I'm finally gonna do something useful with my life.
All I gotta do is learn UI. Easy peasy.
I spent the next week or so experimenting with my code, coming up with ideas for the app in my head and of course, telling all my friends about it. Bad habit, I know.

Guy1 was about to meet Guy2, so I asked Guy1 to tell Guy2 about my idea. He agreed. I reminded him again later that day, and then again in a text message.
The next day, I asked him if he remembered.
Guess what.
I asked him to text Guy2 instead. He came back to me with Guy2's reply: "Why won't he send me a message himself?".
So I contacted Guy2. After a while, he replied. We had a short, awkward conversation. Then he asked why he should prefer a new app over the existing replacement.
He activated my trap card. With a long chqin of messages, I unloaded everything I was gathering in my mind for the last week. I explained how he could use the app, what features it could have and how it would solve his problem and improve his product. I finished it off with the good old "Yeah, I was bored😅" to make the whole thing look a bit more casual.
Now, all that's left to do is wait.
...
Out of all the possible outcomes to this situation, this was both the worst the least expected one.
I'm not familliar with the English word for "Two blue checkmarks, no reply". But I'm certain there is no word in any language to describe what I'm feeling about this right now.
By that point, Guy1 has already made it clear that he's not interested in being my messanger anymore. He also told me to let the thing die, just in case I didn't get the hint. I don't blame him though.

It's been almost a week since then. Still no reply from Guy2. I haven't quite been able to get over it. Telling all my friends about it didn't really help.
Looking back, I think Guy2 has never realised he has that problem with his product.
But still, the least he could do is tell me why he dosen't like it...
"Why won't he send me a message himself?" Yeah, why really? HMMM :thinking:

You know what? If I ever somehow get the guts to leave my home country, I'm sending a big "fuck you" to this guy.

My boss has a weird habit of asking my opinion and then proceed to choose the worst option. So one day he asked what Java for Web framework we should use I said we should use Spring, we are currently using JSF. Then he asked what version control we should use I said git. Guess what, he decided to use SVN. Next time I'm going to say the worst option maybe that will make him choose the better one.

Before rant (introduction): I'm the kind of dev that is a procrastinator by default, it takes me a huge amount of effort to avoid this bad habit.

Rant:
So, I'm going on vacation next week and finished all my shores on Monday. As I'm about to go on vacation, my team leader is avoiding giving me work so that it doesn't stay half way when I leave.
The problem is, this is the third day that I arrive at the office knowing that I will be there for 8 hours wasting my time not doing shit and looking at the screen!!!
The worst part is that if I get this bad habit going, it will stay and I will start to procrastinate a lot if I don't work to do fast

My worst habit(?) is probably loving to "waste" time, making api uri builders.
so I can chain a couple of methods instead of just typing out an uri :p

I need to add new feature into the program which I wrote years ago so I start digging up the source code. The project is written in a language which I no longer code in.

That code is really poorly written with most of them don't have tests. I also find out that previous self is really a genius since he can keep track of huge project with almost no documentation.

To make matter worst, there are unused components (class,feature) in the source code. "Current me" have a policy of "just adding only a feature you need and remove unused feature" but it seem the "previous me" don't agree with the "current me".

The previous me also have the habit of using writing insane logic. I can remember what particular class and methods is doing but I can't figure out the details.

For example one method only have 5 line of code but it is very hard to figure out what those do.

The saving grace is that he know the important for method signature and using immutable data structure everywhere.

I was under the influence of caffeine and have a constant sleep deprivation at the time (only sleeping about 4 hour every day) so I can't blame him too hard.

I can't blame him too hard, right?

Could someone invent a time machine already? Invent time machine not to save the world but to save the developers from himself.

I think my worst habit is that I create too much DRY code. Sometimes code gets repeated when I'm just too focused on getting a feature to work and makes it hard to refactor later :/

Best: Learn a lot of stuffs, managed to make reading as a habit (tho still limited to tech and startup yet), did an awesome intern n learned a lot from there plus got an invitation to work there, happened to pass exams (which some of them I was horrible at) and primarily found devRant! :D

Worst: got most of the load in a team bec ppl see I am more credible n can do stuff properly, has to stay another semester in this country (foreign student stuff)

starting out with a couple coroutines to spare is literally the worst bad habit I've got from golang and that's a compliment. rust, for example, got my over engineering OCD thru the roof!