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
-
"should I commit this? nah let's just implement this huge feature first and commit that clusterfuck of changes with a commit message «changes»"8
-
Starting 124,086,667,135,647* projects, but never actually finishing them.
* Note this number is an estimation and may not be entirely accurate.3 -
getting bored of personal projects and stopping it after being halfway through, or even when they are almost complete7
-
Not using blockchain to color my cryptocurrencies pink so that my AI knows which cloud computing would be best for GDPR1
-
Often saying fuck it when I've got a project and I kind of really need to use git but I'm not good with it so I just go back to good old scp again 😅11
-
Writing more infrastructure than product.
Look, my application requests and transforms data from a single external API endpoint, it's just one GET request...
But I made an intelligent response caching middleware to prevent downtime when the parent API goes down, I made mocks and tests for everything, the documentation is directly generated from the code and automatically hosted for every git branch using hooks, responses are translated into JSONschema notation which automatically generate integration tests on commit, and the transformations are set up as a modular collection of composable higher order lenses!
Boss: Please use less amphetamine.5 -
Bad dev habit to unlearn:
Impostor syndrome before starting a project.
Don't think a lot before diving into a tough project. Just jump in. If you second guess yourself about being ready, you'll never do it. Either you're already good enough or you'll figure out what you need.
I wasted way too much time before starting to write an AI chess engine but it turned out a lot simpler than I expected.2 -
Some devs like to write meaningless or too general commit messages.
Stop it. Get help.
Call 0800-GITGUDBOIII where real experts talk version control.10 -
So many bad dev habits...
But the one that results in the biggest headaches afterwards?
Me, when given a problem and being asked an estimated time: 'This shouldn't be too hard, gimme X to do it', only to later find out it's way harder than i imagined.4 -
When I say I'm coding, what I *actually* mean is screw around with my .vimrc and color scheme for 6 hours.2
-
Completed Flexbox Froggy.
Finally Learned FlexBox , would recommend it 100%.
From: flexboxfroggy.com
12 -
I understimate always how long tasks takes. Because of the fear that it is expected to be done quick.
I should unlearn that. And learn to communicate the time it really takes: at least doubble the amount of time of what you're thinking it takes.4 -
Skipping unit tests and documentation ...
I'm starting to recover after not writing a single test for the first 6 years of my professional carrer (wasn't taught in school, didn't know where to start, man I should have really found a mentor earlier), and barely any documentation (I was the sole developer for several years, and just didn't get into the habbit).
Unit testing is still not a habit, but now I have the first tests to serve as an example and an idea what/how to test at least, and I try to get every new "framework" function/class at least commented properly.
Wish me luck2 -
Project hopping ( basically never completing a project) and wanting to learn everything (I always end up not starting on anything)1
-
You know the thing where you put "password":" asd" in a json file to test locally and then push it to the server.
You know when you push to git and not add the generated files to gitignore.
You know when you use "asd123" as salt.
You know when instead of using triggers, you do everything with code.
Yeah...1 -
Staying up late night and sacrifice on sleep to complete the task at hand. A good night's sleep will result in good quality code.1
-
I guess most of the things I do are a bad dev habit?
From not commenting stuff to commenting in German to copying stuff without looking at it, procrastinating a lot, not starting at all, bad naming of variables, bad... Everything? Idk, I have a lot to learn4 -
*Writes code, doesn’t test* “Ah this works, I’ve done it before”
*Finishes project, runs test, errors everywhere* “FUCK!”
I do it on non-important projects... but I need to stop before I start doing it on important projects 😑2 -
Allowing programming to take over my life; if it's not work, it's side projects; forgetting to live a life away from work in some form.2
-
I stay up very late. It’s gotten later and later as life goes on. I’m tired of being tired. It’s so exhausting.1
-
Deleting debugging/logging lines instead of commenting them out, when there is 95% chance that I will need them again3
-
Write idiot commit messages that I don’t remember what they mean eg. “Added function x” instead of “Update {filename}”3
-
I keep sacrificing readability for cramming a shitload of instructions into one line. The same goes for writing comments.
-
Rewriting the entire codebase anytime I learn that I was doing something wrong.
Rewriting entire functions whenever I see that my coworker coded bullshit on the fly.
In a nutshell, I should stop trying to rewrite everything!2 -
After being an active developer in the industry for about 5 years, I still have some bad dev habits on which I'm working on:
- Starting off with the code first without a proper design in mind/paper. (Trust me, I'll always regret of not having a proper design later)
- Writing long method bodies and not refactoring them later. (Because sometimes I turn out to be a lazy ass)
- Duplicating code in some places without reusing some.1 -
Not commenting and documenting as I write. I always wait till after and then I get bored of it while doing it...
-
Pressing ctrl+s in sql dev when checking packages.. you accidentally press space or sth and later ctrl s it compiles.. then shit gets real when you accidentaly lock up everything on prod db..2
-
Start coding at 21:00 and stop at 01:00 the next day because inspiration for coding usally only comes at that time
-
I suppose I should stop randomly naming variables and keep the randomness throughout the whole project
example: int psnhiwovb;
...I still have a project with such random names.2 -
Which PC / Mobile Games you guys are playing?
I was playing League of Legends till last month but it's too TOXIC and Riot doesn't care.
So I stopped playing it from last month and started 100daysofcode challenge but as a gamer I can't survive without good game (lame).
Now I think I lost my habit of playing game like drug addict( but Still when I am bored with coding I prefer to watch YouTube).
What you guys do when you are bored with coding??15 -
Distracting myself from something I should be working on. Then continuing to code. But I bout that pc a few years ago. It also compl—
Wait, what was the topic again? -
Forgetting that pencil and paper are the original OS and that spending even just an hour doodling flows and writing out ideas, models, biz logic, and formulae can save me literally DAYS of hassle...1
-
Fuck I wish I knew what to do about low motivation!!! I have some ideas I think are really great, some that might be profitable, and fuck I just don’t do any of them. I spend more time panicking about what to do than anything else. But damn so much time wasted when I just needed a little guidance or a little planning or a little like less than $100 more money. That frustrates me to no end.
There’s so much bullshit to everything. This does follow up to my wk106 rant, where I’m trying to rationalize the tons of code that are behind the smallest features. How many thousands of builds go into a deploy. Just swallowing how much rite in software.
I feel like a failure at my job at times but what sucks is I’m just in the middle. Not the most experienced dev, not the least. I’ve got my feet wet in a number of things, but not a solid enough stack for a lot.
BUT SOMEHOW I GOTTA BE MOTIVATED TO LEARN. FFS I CAN DO BETTER BUT MY INSIDE IS BROKEN SOMETIMES AND I JUST WANK OFF FUCK GET IT TOGETHER.
Yea, I fight with myself a lot. I have a big ego and I’m a piece of shit at the same time. Idk. That is annoying too. If only I could get really motivated and focused on some of these projects I could do amazing things. I’ve never struggled with a subject I applied myself to. I just wasn’t motivated. I don’t know how to fix it and I wish I did. I also don’t know what the end game for me holds.
This whole complex really scares me for later life. I will have regrets because my mind builds impossible plans for good, but if I achieve any of it I WILL THINK damn I should have not dealt with this and done x. Like I could make world peace but be like damn coulda rebuilt cars or some stupid shit.
So I’ll conclude with that I’ve done a lot of jobs around the house, and yes working with drywall sucks. So sometimes I’ll think about that. But damn. That doesn’t last because I know I can do it well if I apply myself.
All this leads to getting overextended which is another huge motivation killer. I’m trying to learn self control and focus. But also I need small victories along the way. Very annoying.
Well at least I was motivated to finish this rant. I have a few weekly rants I wanted to participate in but couldn’t even find the motivation for that. There was a toxic person in my life then and I’m slowly getting back to normal but I know that even normal me struggles with motivation. Plus that toxic person was my friend and I’ve lost a lot of (long term) friends recently and that is a real drag. But they needed to go. But I wish they had just shut up sometimes then they wouldn’t have been so toxic. But I digress.
I know I have so many ideas I can’t do them all even if I am motivated and for some time is of the essence.
So look out for some collabs. And grab that motivation wherever you can find it.1 -
if (statementA && statementB > statementC || statementD < statementE && statementB != statementC) {
// do sth
} -
Always saying "yes I can do it" even though Im already backlogged with work out of a fear that Im unreliable.2
-
I suck as Excel so instead of using it as every normal person I prefer writing a tiny script in Python to do the job...2
-
The fear of making mistakes and overthinking, and thus, staring at a black screen for hours until I start doing anything.1
-
Not caring about code styling and just committing because whiny people annoy me. It works; it works. I should probably abid by code styling standards and do a precommit but bite me 🖕🖕🖕2
-
I find it so difficult naming my classes, and Id’s in html and naming my variables in both JS and PHP. They are either too short and vague, or too long and specific. Haha Sometimes I wonder if I should use underscores or camelcase :( hard choices! >.<1
-
Forgetting to git pull before modifying and pushing stuff and then having to resolve a f*ckton of conflicts1
-
Always read the Stack Overflow thread carefully otherwise, you will'be the one asking a question next time.
-
The "just do it" mentality that comes with tight time constraints.
It's been way, WAY too long since the last time I just sat down and thought about design with patience and well-intentioned dedication. -
Me - Ooo I've got this idea ! This will fix this "No ones" problem in programming.
(Thinking this will change the programming for everyone)
Starts Coding......
Few minutes later ...Searching stackoverflow for silly syntax errors.
...Finds a 2 years old project from some guy, who already finished working on the idea and answering question as "This is a bullshit idea!, Never try to make something like this."
Me - (Suffering from existential crisis)2 -
A bad dev habit I should unlearn?
How about being too stubborn to take an idea out back and put it out of it's misery. You know what I'm talking about. Got some elegant idea in your head, it looks so pretty and masterful. You begin to implement it but straight away, things start looking pretty fucking ugly. You persist though, and persist.
Sooner or later that pretty idea looks like Donald and Hillary decided to spawn a love child. You close your eyes and grit your teeth, unwilling to put the abomination out of it's misery.
You stop and finally open your eyes to look at what you've done. A hideous beast with Gary Johnson's nose, Bernie's voice. Donald's hair, and Hillary's lips stares back at you. Yeah. Now you've wasted hours upon hours and only have a mistake worse than the 2016 American Presidential Election to speak for it.2 -
Deciding to make the website I'm working on a one pager with calls to API.
Why did I decide to make such an extensive API. 😅
API functionality includes:
user endpoint:
- log in/out
admin endpoint:
- edit user
- create/delete user
- create (sub)menu categories
- create items (install/test/image)
image endpoint:
- create image (of machines in array)
- restore image (of machines in array)
install endpoint
- install machines (Windows/Linux)
test endpoint
- auto-test (array of machines)
- test (array of machines, test)
Then the machine endpoint:
- if action in table then do action3 -
Debugging and fixing other shit when needing to work on an enhancement.
I think it's procrastination, but in the end the thing I'm fixing actually works as intended, so I don't have to lay eyes on it anymore... -
Opening a million tabs on Chrome, inwardly saying, 'I'll get back to you later' after briefly reading the first few paragraphs
-
Being an perfectionist.
Refactors on refactors on refactors, thats why I like a manager who keeps me from just that.2 -
I have two bad habits that I try to get rid of:
- Googling instead of directely searching in the product documentation.
- Copy/pasting code instead of typing it. -
Bad habit as a developer I wanted to unlearn is To not to keep posting rants in front of my Team Leader while working who is discussing about project with me..
-
My worst default is laziness.
I live in the UE. And in 5 days I reported 15 GDPR breachs (most recruters), so i'm starting to check how could i automise this action so i can do it by a RESTAPI call, and create some kind of 'share' link so other people can report the same business for the same reason... All that only because filling the cnil form is a haslle...
I have a script to classify and auto respond to stupid/shitty questions...
I make short alias for every command i use more than 10 times....
Conclusion :
Being Lazy take A LOT OF WORK!1 -
Not using all my time. I really don’t apply myself sometimes. Sometimes that means not using work time efficiently, sometimes that means I get stuck on a simple problem for too long because I don’t think through it. Also, I’m trying to love coding more. It takes a lot of code to get a small result sometimes, and that’s ok. I got hooked on being able to do big things with little code from the start. As we get better we know there’s more that can be done, but we are more familiar with just how much work it really is. At the same time we are more capable than ever of doing it. Just gotta embrace the suck, then love your finished product.1
-
"I'm going to learn and use <cool new Javascript framework/library> for this project!" then having to try and learn it, only for the new project to eventually use jQuery again.1
-
Waterfall.
I string dislike the waterfall methodology and much prefer agile or scrum. And it's incredibly difficult that upper management only understands waterfall while claiming to know agile.
Meanwhile they want things completed by deadlines that are only possible with an agile approach. So you have a mishmash of upper management running waterfall with impossible deadlines and developers trying to meet those deadlines running in agile.
Anyone else have this problem? -
Direct implementing major functionalities without learning core/basics concepts while learning any new framework or library.
-
When I build a large project, I open devRant, Imgur or youtube while I wait, but get so caught up that I don't realize when the build is done and spend way to long surfing when I should be working
-
I should learn how to stop at dead end.
Sometimes I am too deep into problem and I just cant stop programming, debugging and thinking about it. It would be better to make a pause for like a hour, turn my brains off and later start again but I just cant. Even if I leave my desk my brains remains at the problem. Sometimes I want to stay at work to solve it... xD Eventually I solve the problem and after a good sleep I rewrite and refactor all code becuase I found a better solution in like 30 mins. It frustrates me because I dont know how to turn off...
Anyone else?1 -
Leaving Discord open while working on personal projects. When switching between windows it’s all too easy to get distracted by a spicy shitpost strolling by...
-
Not starting on work until I barely have enough time left. Then pulling multiple all nighters to deliver on deadline
-
Something you really should not do:
*adds a new feature*
*build & run*
*See no difference*
Me: "Hmm.. Maybe 1 is not the best test integer, let me pick something higher..."
*build & run*
*INTEGER OVERFLOW EXCEPTION*
Feel free to share your "let me choose anothee test integer"-stories, which gone terribly wrong.1 -
Understand problem
Write solution
See it work on browser
Delete/comment solution
Write tests
See them fail
Restore solution
See it work on testing -
EDITOR=nano sudoedit foo
Spare me please…
It's not that I don't know how to use vim/vi, I'm just lazy to get used to it…1 -
Wanting to remake the wheel.
p.s. Not sure if it is bad or not as Ive learned a lot, however, there are better alternatives3 -
Perfectionism... I often refactor my code because I always see something that could be "done better" in my own work, which can slow me down if I'm not paying attention to my main task.
If I could stop time I would perfect my code all day, but that isn't realistic. 😂
Doesn't apply to dev work only, I've had to learn the art of not giving a shit about every single detail in many other disciplines. I just love getting things done really well. -
"I'll make a library out of this part of code, so it'll be portable! But another day, I have to make the whole thing work first"
*1 month later*
"Alright, why are there 4 different versions of this class lying around?" -
Updating WordPress plugins and pushing directly through Test to Live without stopping and doing regression tests on Test first. “It’s just Yoast SEO. What could go wrong?”
-
Making classes and functions without commenting what I expect each class and function to do. Which means that my classes and functions have really long names.
Example Code:
Class ReallySpecificClassToWorkWithThisFramework { ...
public void DoThisActionInTheFramework (obj TheKeyToTheWholeFunction) { ... }
} -
My fingers travel a little bit too much on the keyboard.
I think I may get an Ergodox-ez and fix this by force!1 -
Constantly changing conventions for everything, like naming and code formatting conventions.
And the worst part is, I do this several times during one project.
Either I have a project with different conventions or I have to redo a lot.
Most of the time I try to do the last and this costs so much time -.-' -
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 :/1
-
Keeping the part time offer of my current job to continue doing school full time, instead of reversing that and not having to pay for school3
-
Better get started...oh look at this shiny new piece of tech. 3 days later with evaluation done on each usable tech alternative crunch the solution together in record time with tech most similar to your previous one.
-
Make the comments of a piece of code more complex than the code itself. I don’t know how I do this, it’s like a instinct or something like that1
-
*deletes env var* "I'll just hard code this to localhost for now, my ci/cd pipeline will setup everything later"
*Pushes to master, forgets to undo*
Aw fuk,
I should of just changed the .env file -
Too much googling.
This is a great skkll and I know it leads you to amazing links and resources, but currently i have a list of things to work upon and it has crossed a timespan of next 2 years!! -
Create and release a complete app (or join a open source protect) instance of learning new technologies :/
-
Leaving things out of VCS. My usual folder structure is like this:
- Project name:
|-- env (virtual environment)
|-- Project name (git repo)
\-- (keys, credentials, etc.)
It makes sense, but after a while, more and more important stuff starts piling up in the outer folder (not version-controlled). -
I'll do the tests later on it'll be fine. 3 releases on, There are bugs everywhere - I cannot handle the regressions. Why'd this happen..Yeah.. Really need to do some proper TDD at some point.
-
1.Ignoring the warnings during compilation of program and executing it.
2.After random crashes,trying to fix the system by handling errors one by one. -
Being undecided, my first attempt to make a website was first made with django, then pylons, then pyramid (I know, pyramid is the "newer version" of pylons, but they are different enough to be considered different things in my opinion), my first real attempt at making a game was first made with pygame + cython, then cocos2d-x + cython, the cocos2d, then oxygine, now trying to learn unreal engine
-
Commenting and forgetting to delete before merging to master, only to create another branch just to delete these comments or put TODOs. 😑😑
-
It's not an exactly habit, it's a error that I sometimes do. Type 'funtion' when I defining a function. Then the console logs an error and I cannot identify what and where is the error in the code. After search 1/2 hour, I realize, and then I feel a pathetic dev :'v1
-
Keep scrolling on facebook while expecting there is a message from someone.
Then later, projects delay
Top Tags
Weekly Rant
View