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 - "laziness"
-
I would absolutely love it if people would write their own stupid code instead of blindly mixing everyone else's mental diarrhea together and pouring the resulting mess into their bloody stupid IDE. At least then I could insult them properly. As it is, they're outsourcing their fucking stupidity to the lowest fucking bidder and then bragging about how quickly they get everything done. And management eats it up! No wonder everything is a slow, tangled, unmaintanable mess.
I can't fix much of anything because almost none of it is in my control. It's all autogenerated bullshit glued together with laziness and poor taste. "But Root, why is fixing this taking so long?" Gee, I wonder why. Maybe if someone had built it somewhere in realm of correctly the first time, it wouldn't have all fallen apart when someone looked at it the wrong way!
Seriously, there's no way this pile of stale fertilizer could have passed QA.rant idiots import * fragile monstrosity leggy devs why code when you can steal no independent thought npm mentality9 -
!rant
I received a pair of complements on how well I run team meetings after an engineering all staff this morning. Received a similar comment last week.
Someone asked “what’s your secret?”
I reply “Laziness”
“What?”
“I’m lazy. I don’t like meetings most of the time. So when I run meetings, I run them so that they’re over as fast as possible”
“How do you do that?”
“By knowing what I actually want”
“What if you don’t know what you want?”
“Then there’s no meeting”
“Well what if y-“
“Hey listen I have another meeting to get to”3 -
So I am a Software Engineer at a small scale company.
I need to coordinate with customers, understand the requirements and design and develope the solutions.
These sometimes include changing the current product a bit and customize it to fit the client needs or maybe creating a plug-in that could work with the current product and get the job done.
I love the research, design and planning part of the job, I would be super focused and will find solutions for complex stuff. Plan it all to the smallest things.
I know the solution so I can think of what code would be there what would be needede whats already there etc.
But when it comes to coding the solution my laziness kicks in.
My mind is like you already know the solution why you need to code it to.
Then I start procrastinating and end up putting myself under a pile of stuff when the deadline approaches.
FML3 -
If you’re struggling with productivity:
[1] Wake up early & Exercise
Waking up early means getting most of the work done as soon as you start your day. This sets a routine for you.
Doing a high-intensity workout early in the morning can kill laziness and make you feel productive.
[2] Divide the day into three parts
Do the most work in the morning hours i.e 6 am to 11 am.
Keep the 12 pm - 3 pm for work that requires less energy. Evenings can be utilised to finish minor tasks.
[3] Make a timetable
A proper timetable or To-Do is a good way to keep a track of your daily routine.
Tick off the work you've completed and you'll feel you've been productive.
[4] Follow people who motivate you to work
If you waste time scrolling on social media, make sure to follow people who instantly motivate you to work and take action.
[5] Update or shift workspace
Your workspace is where you spend most of your time, so make sure it makes you feel motivated to work.
In case you are bored of your workspace, shift it to a new room, preferably that has windows for fresh air.10 -
Hey, I actually calculated and averaged everything, and I found out I only spend about 43.4 repeating percent of my time awake actually working.
Can you all calculate yours as well to see if I’m a lazy slob or if this is normal?8 -
Utility libraries, because I actually get to see my life improve because I have them. Creating new projects becomes easier because I put parts I reuse somewhere else.
There was an old config file generator/manager I kept using for a while, some string conversion libraries between formats, some REST/WebRTC API wrappers, I have a web audio API I create tunes with in various projects. CI/CD scripts for laziness so I never have to know how to set anything up again. Lately the thing I'm most happy about is I turned some free text saving service into a makeshift database and it's been working well for about half a dozen projects now. Wouldn't handle large amount of users but can't beat free and easy.
I also find merit in prototypes/old projects, because I can reference random things I did in them in newer unrelated projects. Things too small to warrant their own utility library, argh!