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
Search - "wk255"
-
Bad dev practices:
1. Forgetting to version control some fun project i am doing for a long time and then commit everything at once. And forget about it again..
2. I probably have too much love for abstraction. So i abstract stuff just for the fuck of it to the point my friends dont even understand what the program is for.
3. I have no patience and due to that i lose motivation when i think of some idea that is big.
4. I cant keep my ideas small enough, and i dream too big until problem3 kicks in, and then i drop the entire idea.6 -
Bad dev habit: using a bazillion console.log/println like a caveman instead of using a proper debugger.9
-
Bluntly telling management that they're wrong, full of shit, and need to quit doing stupid things instead of just smiling and nodding and taking the paycheck. SPOILER ALERT: After 20 years in industry, they're NEVER going to change. They're just going to keep doing stupid shit. The best you can do is smile and politely point out that it's a problem. Then, look out for your own concerns and make sure you don't have to suffer with their bullshit decision as best as you can.
-
Overthinking and premature optimization. God damn them both! My mind completely freezes trying to come up with the best approach without actually trying or typing anything, only thinking.1
-
Bad habit?
Procrastinating important tasks because they're not fun, then stressing right before my deadlines..2 -
Create a library without writing a proper documentation.
1. I'm lazy.
2. No one is going to use it anyway other than me. -
Forgetting to switch the git branch from master to back to Dev after committing. If I had a penny!4
-
The task: Catch and log this specific error in this one function.
Me: While I'm here, let me just -
git: 12 files changed3 -
Adding more random half-started projects to my hard drive.
I would put them on github but then I'd have WAY too many reps that don't function and I'd feel like I'm wasting storage on github.
At some point I need to get motivation to work on some of these6 -
Forget about committing often and end with multitudes of changes. Which then leads to writing a generalized commit message.4
-
Choosing jobs that doesn’t have much volume of coding actually. I am gatherin rust-I wish there was a programming language for me...1
-
I always work too much in bursts. Long days of intense work when I’m deep into something, skipping lunch and breaks. Then short days when I take it easy. Would probably be better to work more evenly.3
-
Working all my cores in parallel; working on multiple projects at the same time without finishing any project.2
-
i waste time learning a language or a framework ik i cant ever use at work because i like the way it "feels" and looks.
while others learn stuff we actually need to use at work and will end up outranking me -
Being lazy sometimes and writing type definitions after I’m done developing something rather than before (hence wasting time as doing that work is meant to help with the development process in the first place...)