In the darkest of days, I discovered how to remote login to my computer at work through the company vpn. I then proceeded to work overtime at night in secret for a week or so, writing documentation and refactoring code.

I finally woke the fuck up and realized that I shouldn't be obsessing over proprietary codebases that do not belong to me, and I should put this misguided energy into my own projects.

So yeah, as a bad dev habit I'm working on fixing, this fits the bill.

Not really a dev habit, but a habit many devs have.
My beyond fucked up sleep schedule.
SLEEP CAN
SUCK
MY
ASS

I've woken up at 8 and went to sleep at 12 for two days, and I'm beyond happy with the purely accidental progress I've made, really hope to not fuck it up this time like always.

giving up on projects when i run into problems above my knowledge level

Habits to curtail

Not enough beer

I need to stop sacrificing readability for smaller amounts of code. What looks good to me isn’t always best for everyone and that’s a fucking tough pill to swallow.

Bad dev habit: ranting on Devrant.

starting way too many projects

Trying to get my 'patience for Idiots' threshold back up to 15 minures. Not easy.
The problem is - you need to listen to them talking for 20 minutes before 30 seconds of relevant and actual info comes up.

Bad dev habit I'm trying to fix?

Code addiction.

Really should stop not caring about access modifiers. Nearly everything I code is public.

More work-related than dev-related:
- Saying "yes" to extra work more often than necessary.
- Wanting to do everything myself and not delegating enough.
- Getting too stressed out.
- Avoiding conflicts and confrontations (even necessary ones!) and not being assertive enough.
- Overthinking everything.

Bad dev habit I am trying to fix: copy-pasting code without understanding

Undoubtedly the most common mistake that devs do : Ignoring your personal health, be it mental or physical.

I almost went through a burnout before realising things need to change.

Changed my lifestyle upside down after that
- Switched from wfh to an office job
- I cycle 12kms a day now
- Got a standing desk for myself to be more active
- and have a journal where i literally dump everything off my brain

me debugging instead of sleeping🥲

Creating a git repository and forgetting to commit and push. And not only after ending the project or nearly ending the project...

And fucking commenting stuff

Not really trying to, but probably should try to fix this bad, bad habit…

I keep wanting to fix and improve everything - and I keep taking notes, writing action plans et fucking cetera to the point the amount of work that should be done and I want to do is driving me insane. And they should all get done now!

In short, I should really either learn to focus on just one thing at a time for a meaningful period - or just cease to give a fuck. Either could work.

Bad dev habit…

I am still learning like super fresh —
Second week of class.

But I am also looking at things and getting overwhelmed because I’m like idk wth that is.
But when I end up learning it —
I’m like ohhhh!!

I just overthink everything !!!

I think, right now, it's bitting more than I can chew.

I get my hands on way too many projects because they're easy and then problems pile and I end up being behind schedule on everything.

That, and maybe sometimes subconsciously thinking I'm invincible. It's a direct psych response to those telling me I can't do shit, and then I do shit out of pure stubbornness, and then I have super-confidence for a short while. (Even if I don't show it)
I just don't think it's healthy.

Not really giving a f*ck about pagespeed and lighthouse reports.

And overthinking styles…

One of my bad dev habits is that I tend to take up too much work because a lot of devs I had to work with seemed not competent enough. It's a bad habit because I get way overworked which influences code quality and deadlines.

I have to learn to trust more in others and give up some responsibility... it's hard though.
I think a big influence on my mindset has been that I never worked in a team bigger than 4 developers and I had way more experience in web dev than the others.
I sometimes may appear as an arrogant prick, but it's not intentional.

wish can do coding in fix hours :(

Learning react .. just took one cup of tea in morning.. and dang its 8pm :( No idea about the time.. react giving me hard time. maybe am newbie ..

Hope so I learn this Single Page application

Not leaning on unit tests. I usually write them after testing my code manually, and lose time for testing feature by hand.

Laziness

Going to long trying to figure it out myself before asking for help.

Fixing out of scope/unrelated code quality issues when working on bugs/features.

Especially with older projects where pretty much the entire code base is a quality issue.

Resizing my partitions without backup and moving them between disks.

Never had a failure but i guess it could be risky

Not consistently git comitting (and pushing to repo). Sometimes I wonder if I'm in fact a masochist.

Showing up to work every day after 25 years of this knowing that I really kind of suck at my job and feeling like I’ll never get to a point where I can say I’m fully caught up to the level of knowledge others I work with have or that I’m expected to have. I suppose this is a bad habit of attitude but it seems to be an actual reality for me with every passing day, week, month, and year. It’s all just too much and my brain just isn’t as agile as it once was (and it wasn’t all that agile to begin with).

I start a project that follows the best architecture, best practices, etc..

i suddenly stop working on it until 3 days pre-deadline. at which point I end up building the shittiest, hackiest, thing that works enough to give to the client on time

stop thinking big and trying to fix, predict and solve every problem and accept the fact that I lost the battle so I can focus on small things instead of big ideas that would never happen

cause maybe just maybe bunch of small things can at some point shape big idea

not sure if actual bad habit, or just a natural consequence of what i'm writing often being de-facto "exploratory code" so the "bad habit" is actually the right choice, or...

but very often when i finish a functionality and look at the first version of the code, and realize how bad it is, and how it blocks me to implement following features... rather than just fix/improve that code, i just want to nuke all of it and write it from scratch again, and "better this time", because it seems like much less work and effort than trying to gradually fix it "in-place".

it definitely feels like a bad habit though, because it often results in me deleting and implementing to completion the same thing 4 times in a row.

Still not using versioning even though I'm the only coder. I have a dev and a live version of the site and once in a while (like early this morning) I update the live site by mistake, writing over the safe file with the development one :S

I guess I just try to make a features list for "my next thing (now 3% smaller!)", instantly become a customer, demand way too many features, then get lost in the to-do list aand I'm writing another devRant. Nice.

Not going for the obvious (and usually easy) solution first and then iterating on it.