Front-end developer's to-do list :
☑ Climb Everest
☑ Learn how to speak mandarin
☑ Become god
◻ Vertically center something in CSS

As a developer, sometimes you hammer away on some useless solo side project for a few weeks. Maybe a small game, a web interface for your home-built storage server, or an app to turn your living room lights on an off.

I often see these posts and graphs here about motivation, about a desire to conceive perfection. You want to create a self-hosted Spotify clone "but better", or you set out to make the best todo app for iOS ever written.

These rants and memes often highlight how you start with this incredible drive, how your code is perfectly clean when you begin. Then it all oscillates between states of panic and surprise, sweat, tears and euphoria, an end in a disillusioned stare at the tangled mess you created, to gather dust forever in some private repository.

Writing a physics engine from scratch was harder than you expected. You needed a lot of ugly code to get your admin panel working in Safari. Some other shiny idea came along, and you decided to bite, even though you feel a burning guilt about the ever growing pile of unfinished failures.

All I want to say is:

No time was lost.

This is how senior developers are born. You strengthen your brain, the calluses on your mind provide you with perseverance to solve problems. Even if (no, *especially* if) you gave up on your project.

Eventually, giving up is good, it's a sign of wisdom an flexibility to focus on the broader domain again.

One of the things I love about failures is how varied they tend to be, how they force you to start seeing overarching patterns.

You don't notice the things you take back from your failures, they slip back sticking to you, undetected.

You get intuitions for strengths and weaknesses in patterns. Whenever you're matching two sparse ordered indexed lists, there's this corner of your brain lighting up on how to do it efficiently. You realize it's not the ORMs which suck, it's the fundamental object-relational impedance mismatch existing in all languages which causes problems, and you feel your fingers tingling whenever you encounter its effects in the future, ready to dive in ever so slightly deeper.

You notice you can suddenly solve completely abstract data problems using the pathfinding logic from your failed game. You realize you can use vector calculations from your physics engine to compare similarities in psychological behavior. You never understood trigonometry in high school, but while building a a deficient robotic Arduino abomination it suddenly started making sense.

You're building intuitions, continuously. These intuitions are grooves which become deeper each time you encounter fundamental patterns. The more variation in environments and topics you expose yourself to, the more permanent these associations become.

Failure is inconsequential, failure even deserves respect, failure builds intuition about patterns. Every single epiphany about similarity in patterns is an incredible victory.

Please, for the love of code...

Start and fail as many projects as you can.

// TODO hahaha

I can so relate to this, though the scenarios are different. Makes me mad.😾

//TODO: Laugh

Every. Single. Time.

// TODO: Placeholder. Replace with a better solution

Never does

I found a //TODO in our companies code that's there since early 2016.

The company was founded in early 2016.

Found this 2 years old beauty today:

public boolean hasPermission(User user, Permission permission){
// TODO
return true;
}

The author quit last year.

TODOs top 5

[x] create README.md with TODOs
[ ] add tests
[ ] write documentation
[ ] automate deployment
[ ] improve security

Me and my love-hate Linux.

I lost virginity really early. In the age of 5 it was my first time with windows 95. I spend almost 10 years with Windows before something happened that would change everything. I met Linux. Her forename was Arch. I had a crush on her right from the beginning. It didn't take long for me to abandon windows. Arch had everything I wanted. She had latex which was pretty hot and looked simply and elegant on her. Sometimes she was really hard to deal with and almost drove me crazy, but I knew I fell in love.

Until that day. I had to write a short paper which was quite fun and Linux helped me alot. It was a breeze to work with her. The evening before the deadline she was quite thoughtful. She sometimes was, so I thought it'll be alright, but this time was different. She struggled a bit, so I put her to sleep and she never woke up. I brought her to the emergency lab which was open 24/7. Since no one was there I had todo the surgery myself. After 5 hours I was almost to tired to continue when she finally woke up. I asked her about the things she should remember for me - then I killed her. I started to hate Linux for what she had done to me. The unbelievable stress and horror.

I returned to Windows. Besides that she got a bit more curious what I was doing when and where nothing really changed and she was glad to have me back. I just was happy how simple our relationship was.

One day then, I couldn't believe it at first, I met Archs sister. Manjaro. No matter how strange that is, but it was as if I would meet Linux again for the first time. She was just a bit simpler but as flexible as arch. Since then we are happy together. It seems that we both just grew up a little.

And with Windows? She got even more curious! Actually I have the feeling she is stalking me now, but I don't regret anything!

Just saw this comment in our code:

// TODO: think of a better way to do this

Committed June 12, 2012

//TODO: Finish this later

TODO: <Company Name>

Every day.

I am a PHP developer.

Yeah, "another PHP is awful" rant... no, not really.

It's just unsuitable for some ambitious projects, just like Ruby and Python are.

First of all, DO NOT EVER use Laravel for large enterprise applications. The same goes for RoR, Django, and other ActiveRecord MVCs.

They are all neat frameworks for writing a todo app, as a better-than-wordpress flexible blogging solution, even as a custom webshop.

Beyond 50k daily users, Active Record becomes hell due to it's lazy fat querying habits. At more than a million users... *depressed sigh*.

PHP is also completely unsuitable for projects beyond 5M lines of code in my opinion. At more than 25M lines... *another depressed sigh*.

You can let your devs read Clean Code and books about architecture patterns, you can teach them about SOLID & DRY, you can write thousands of tests... it doesn't matter.

PHP is scaffolding, it's made of bamboo and rope. It's not brick or concrete. You can build quickly, but it only scales up to a certain point before it breaks in multiple places.

Eventually you run into patterns where even 100% test coverage still doesn't guarantee shit, because the real-life edge cases are just too complex and numerous.

When you're working on a multi-party invoicing system with adapters for various tax codes, or an availability/planning system working across timezones, or systems which implement geographical routefinding coupled to traffic, event & weather prediction...

PHP, Python, Ruby, etc are just missing types.

Every day I run into bugs which could have been prevented if you could use ADTs in a generic way in PHP. PHP7 has pretty good typehints, and they prevent a lot of messy behavior, but they aren't composable. There is no way to tell PHP "this method accepts a Collection of Users", or "this methods returns maybe either an Apple or a Pear, and I want to force the caller to handle both Apple/Pear and null".

Well, you could do that, but it requires a lot of custom classes and trickery, and you have to rewrite the same logic if you want to typehint a "Collection of Departments" instead of "Collection of Users" -- i.e., it's not composable.

Probably the biggest issue is that languages with a (mostly) structural type system (Haskell, Rust, even C#/JVM languages to some degree, etc) are much slower to develop in for the "startup" era of a project, so you grab a weak, quick prototyping language to get started.

Then, when you reach a more grown up phase, you wish you had a better type system at your disposal...

Reviewed the code of one of my employees and found that comment: Todo: Improve this if thomas complains.

WHAT THE FUCK
80usd for a multi device to-do application
A TO-DO APP

So before I resign from my job tomorrow I thought I'd talk a little about a couple of things at work that I won't ever tell my boss in person but are generally some of the reasons I want to leave.

---------- warning long rant ----------

1. The CEO of the company finds out I only have my learner's and take the bus, goes on to belittle me about taking the bus.

(It may have been meant as a joke but I was offended, and we don't have any actual HR to complain to)

First off my real reason for not getting my restricted is mostly related to the fact public transportation does the job it needs to, I don't really complain unless the planning is fucked up (Adele concert rant lol) but typically I don't need a car. The other reason is because with a car I'd have to wait in traffic 1-2 hour each way. Also cars cost money which I don't have.

2. CEO buys himself and general manager brand new Range Rovers, you know those giant monstrosities box jeep looking things.

I hate this because I earn $31k, those things probably cost around $50 each (so typically 3 years worth of my wages).

When I had a talk about my contract at the 6 month mark, the general manager (my boss) said he wouldn't budge on my salary (yet they buy these jeeps)

3. I live way too far from work and because of it being Auckland and the current inflation for house prices, the rent prices have also increase, I wouldn't be able to get a house closer to home nor rent with minimum wage :(

4. Though it's not too necessary they mask that the app was made by me, whenever I see an email about the app to potential clients they refer to be as this app guy, and during their presentations they don't really include as part of the reason this app has been developed ( aside from my boss being the client, I came up with some interesting ideas to turn their paper form of the process they use into a digital one, I also did research for the specific topics, something I could have just asked for instead).

5. Old fashioned way of looking at so called "IT", they added fixing computers to my contract which I dread, especially since I'll be close to a deadline and then I get a call to fix someone's computer...

6. They don't seem to want to expand their "development team" to more than one person.

When I give my resignation I have to stay here for a month and I bet people will start to act differently around me, my likely my boss and the CEO. I think the other people that work will understand, given my situation.

I'm planning to for the last month to only do planning for the app they want me to work on, UML diagrams, use cases, Sprint planning (albiet, only developer here lol). Research on the third party libraries we need for the app and generally give the next guy the easiest path to getting the app done.

I want to do this because the Android and iOS app we're done via cowboy programming in a sense. (I don't have too much in terms of documentation and planning aside from a Microsoft planning website setup with to-do of which features are done for the iOS and paper Todo for the Android app.

Alright long rant over, I've got it all written down, glad I'll be leaving this place.

1. See new shiny tech
2. Read install/setup instructions
3. Make Hello World/Todo app by copying codeblocks from documentation
4. Update LinkedIn profile
5. Insist on rewriting entire company ecosystem

Oh wait, thats my horseshit-eating coworker

void procrastinate()
{
//TODO: implement
}

The Lies we tell ourselves ...

My weekend todo list

I was bored so i wrote a simple rager script, todo the opposite of JoshBent´s script. :/ it makes all comment & the rant caps & bold, thinking about adding function to uncensor words such as f*** to fuck etc.

I accepted the job for Machine Learning.

I got hired todo the back end.

I actually do the front end.

//TODO: temporary until re-written in new webapp

A commit from almost exactly 2 years ago 😬

Another joke/meme for you

//Todo means never do

Seen at work in code:

<!-- DO NOT REMOVE CONTENTS PLACED HERE //TODO: Would have loved if some one also had said why we should not remove this -->

Lol

# Day 0:

Me: "Hey boss, I want to let you know that I need this kind of information from the customer for these features, otherwise I cannot finish the project's milestone in two weeks."

Boss: "OK, just continue as far as you can get. We have to get this finished."

Me: "Well, I cannot go any further for these tickets. I need that input. Shall we leave them in todo?"

Boss: "OK."

# Day 7:

Boss: "Whe didn't you start on these tickets in todo?

Me: "As I have told you, I need some information."

Boss: "We gotta get this out of the door!"

Me: "Yes, if we want to meet the deadline, we should. Yet I cannot guess the feature. Also, let me create a column: `to clarify` and move that ticket there. As I have said: I need that information. You have to contact the customer about it and get their feedback.

Boss: "OK."

# Day 13:

Boss: "Why isn't this project finished? There are still tickets open."

Me: "You never provided the information I asked you about."

Boss: "I want an explanation not an excuses."

Me o_O: "This is the explanation. I was asking you on multiple occasions about the required feedback. You never provided it. See the columns name? It's called `to clarify`. We created it last time together. That clarification never happened even though I told you that I need it. I cannot do magic. I can only implement features, and while I can sometimes make intelligent guesses to their use cases, I rather implement their actual ones than my fictional ones.

Boss: "You should have told me."

Me: ಠ_ಠ

that moment...

Devs don't have a bucket list; we have a // TODO list

I now start my to-do lists with
//TODO:

Somewhere in that code there's a
"TODO learn regex"

I hate myself. Really.
Last week I wrote a function to handle file uploads and at some point I left this very useful comment.
Do I know what to fix? Absolutely fucking nope.
I want to punch me from last week in the face

– What are React, Angular and Ember?
– Tools to simplify the building of Todo-lists.

Imagine yourself exploring Medium, looking for some new awesome tools to try out.

You accidentally find the new, promising programming language. It called Blow. It promises itself to be “idiomatic”, “minimalistic”, “simple” and “handsome”. And it also compiles to Electron. You decide to give it a try.

It has its own package manager, simple and idiomatic – every package is “blow add” away. But it’s only three packages available: the “blowsay”, just like “cowsay”, the “this”, printing The Blow Manifesto and “blue”, which is simplistic, simple and minimalistic idiomatic handsome functional frontend framework built with simplicity in mind.

You want to build a todo app, so you type “blow add blue” and press enter.

Following Medium articles written by some guy wearing Ray-Bans, you managed to finally put a todo app together, after seven hours of straight up coding and fighting that simple and idiomatic syntax, trying to make it do what you need. Alright, it’s time to build it.

It has built-in task runner named “job”.

So you type “blow job todo”.

You spending three hours more doing “blow job this”, “blow job that”, trying to blow job everything you see. You’re tired and mad at those damn blow job hipsters created that. You literally suck at programming in that.

Everything falls apart. Things doesn’t work. And after another “ENOENT 0() 0x628 NOT_SUPPORTED”, you give up, admitting that you’ve really sucked at this.

//TODO fix me !

Dream : Write todos.
Reality :
Well, i should conserve paper.
Oh, there is a todo app in my phone!
*Contains ads*
Shit.

I've always been anxious about putting my stuff on GitHub.

However, I did upload a project of mine there.

Thoughs few minutes after uploading it:

"Omg, is anyone judging how bad my code is?"
"I'm sure they will criticize it."
"O shit, I forgot a // TODO in there."
"O shit did I upload my credentials by mistake?"
"Does this commit message sound right?"
"Should I commit more often?"
"Do I commit too often?"

function hackInProduction() {
// TODO: Fix this later
}

Dear mother,

DO NOT FUCKING INTERRUPT ME!
I HATE HAVING TO POP ALL MY WORKING MEMORY FOR EVERY STUPID UNIMPORTANT THING YOU WANT TO TELL ME!
I'm not a processor, I can't easily push my working memory back on the stack.
The int instruction is only ment for priority level 0 events.
It's fine if you put a new item on my todo-stack, just don't interrupt me to notify me, I'll have to pop my stack again!
Also don't change how the todo list should be interpreted, EITHER A STACK OR A LIST!
WAIT UNTIL I HAVE RETURNED FROM MY LAST CALL UNTIL YOU INTERRUPT ME!
ALSO I DON'T SUPPORT MULTIPLE THREADS!

PS: She interrupted me 4 times while writing this rant. It's hell

Found this bad boy in our code just now:
From class SecurityService

public boolean checkAccess(Object obj) {
// TODO:
return true;
}

p.s. it's being used

Callback Hell!

//TODO fix me ..

Leaving TODO comments in code

What are some good developer pick up lines? '#TODO: You' is my favorite :P

// TODO create awesome rants here to entertain other devs to earn lot of upvotes to get a devRant stressball

This is what my code looks like in a nutshell. Stolen from Instagram on a meme page, felt like it belongs here

Opening a documentation page to only find:

// Todo

FML.

Fight against procrastination.

//now I can cross "make your first rant" item on my todo list from 2016.

I wonder how many TODO list apps there exists.

func sleep() {
// TODO
}

When you come to work on Monday as see your Calendar and Todo list clean.

Next level happiness :)

I dont remember this TODO

Yet another story from a dev friend of mine:

He was assigned to a client(he works at an agency, this was a new client) to add some trivial functionality(a share button) to their web app. It was planned as a short task(1 day).

Then he got the source code.
THEIR ENTIRE BACKEND WAS A SINGLE PHP 3 FILE with over 100000 LOC(He couldn't even open it in anything other then vim).
This monstrosity created all the HTML with inline styles everywhere&JS. State was determined with a whole bunch of cookies(one of which was 'admin' and GET parameters, which had no input sanitation whatsoever (obviously vulnerable to sqli).
And there were two comments in this
file:
"TODO: add documentation"
and
"Don't touch this"

When asked why this ungodly beast was created, the client said they didn't want to have long URLs, they wanted everything to be on index.php

1) WHY?
2) WHO WROTE THIS SHIT?
3) HOW?

At least they agreed to let my friends agency rebuild their website.

Also, why does my friend literally work with the shittiest I ever heard of?

Putting todo comments in code knowing it'll never get done.

Bit of a guilty pleasure.

//TODO Tell Jerry to fix this

Me: Who is Jerry?

Who else agrees that the play store should have a section which tells if an app needs a mandatory login to use it ? Like why the hell does a simple offline planner todo app need you to sign-up if you don't wanna use cloud backup. Jeez the user just trusted you by spending valuable time and bandwidth downloading your app. You owe it to him to show him some features of the app before shoving a sign up in his face. As an app developer myself I really think that this kind of behaviour turns off more users than anything else.

So this is a huge fancy screen showing movie times and marketing stuff at my local cinema.

// TODO: get a better camera phone

My brain is melting.

6 hours straight of just Refactoring without a break.

Technical debt is real, it is a bitch, and so are clients to expect to 'see' changes every week.

Boss tells me we need to balance doing work on things the client can play with and the backend code that does it all... 😧ok....

'TODO: remove sample return and connect to backen' As far as the eye can see.

Uncompleted code like

//TODO: write unit test for this

Not proud of it..

Ok, I am fucking finally pissed off...

My current company, I worked for last 1.5 years, for project management they use slack.

Every Monday we have meeting, and we go over every project and talk what must be done. Every project has it’s own channel with some stupid random code name which is impossible to remember because there is hundreds of other projects with similar name.

If there is something todo for dev he just gets mentioned in in channel.

No to-do’s, so basically u have no idea what u need to do, there’s no way to follow progress. Well, of course u can go over each channel and check if u need to do sth, but it takes fucking time. Also because of that u need keep your boss informed all the time about the progress. In others words it’s messy.

To make it worse, there’s usually a few different channels for the same project (1 for devs, 1 for designers, and others for something else like ux or videos).

I brought up this concern to boss many times, and every dev agreed. So for like a month we tried to use flow app, but still everyone used slack + designers told that they don’t like it. So after trial they said we are going to keep using slack. What the fuck?

Now I don’t actually mind their decision, but there one thing that I can’t stand about current method - slack is free, so all history and files gets deleted as time goes. I can’t even count how much times I needed to re-do some work just because slack deleted some files I had put there for later. Or lost some important information about project, that we needed to discuss over and over every month...

3 fucking more weeks left in this stupid company then I quit.

Hello everyone 👋

I see people blaming the developers when you see a crappy software product , saying that they have done a bad job.

But even it could be true also it could be the product managers who didn’t give enough time todo what needs to be done or project scope is too big for the persons knowledge.

I’ve worked in a company where deadlines were so tight I didn’t have enough time to proper UI and Testing. I used to be only developer who has someone experience and I had to train the interns as well. I am also to blame to joining such company but in desperate times takes desperate measures.

And now when i’m leaving the company and I have spend 2 years of my life for apps that I’m not proud of.

Just rant. Please feel free to give ur thoughts

//TODO
.

// TODO: write about shameless hack

My computing teacher says that html is his favourite programming language to teach.

He calls JavaScript Java

Needless to say he's not very good at teaching us html and js.

when you find a TODO in the code, git blame it, and find out it's been there for five years :(

I wonder if someone ever did the //TODOs or fixed the //FIXMEs I left in the code the last place I worked at 🤔

Turns laptop off

Writes key todo list on mini white board for tomorrow.

Thinking occures

Wait a minute, i think i know how to do that!

Turns laptop back on to see if i'm right.

Gets too exited for sleep because thing works

Worst documentation? I have seen worse than that.

// TODO: Show this to my manager next time my app crashes during review

There are 2 kind of programmer.

The first kind is the kind who love to create useful software/product, they would use the same tool/language/technique over and over again but focus on the use case. They end up having few really good softwares.

The later kind have more tendency about clean code. They are passionate about algorithms and design patterns. They can write a todo list app in 100 of different ways. They often pick up new technology, they rarely have something made coz they feel superior knowing different kinds of framework.

Which one is better software developer? Either one is better than the other, coz it's different pursuit. Like Thomas vs Tesla, we need these 2 kind of people in the industry.

guilty...and add a TODO to fix it later

"Task failed. For more info, go to TODO: URL"

fantastic! Didn't know TODO: was a protocol now.

while(freeTime == true) {
if(iHavePlans == true)
waitUntilDone();
/*
* TODO: Fix bug that causes
* coding to call the gaming and
* relaxing methods so often...
*/
code();
}

RANT!

I need to stop Procrastinating FFS.

I have a todo list bigger than my arm and just can't seem to get anything done.

Any tips to beat Procrastination?.

And just don't procrastinate doesn't work 😂.

//Quickfix

//TODO: Buy a replacement switch and fix it in the proper way

Narrator: he never bought the replacement

Software Architect - The person who write code that most of the developers can't understand. Reusable component he says. Motherfucker a simple todo list app has more than 200 functions?!

I tried writing this rant before, but I was (and still am) in too good of a mood so it was lengthy, meandering, and over-specific. so I'll summarize(ish).

summary:
* miscommunication
* working weekends
* incompetence and/or screwy integrations

summary of the summary:
* I can't fix someone else's mess if you don't talk to me!

Summary^3: #TODO: learn telepathy

Shortened rant:
Bossman at work signed up a very lucrative client by promising them something he couldn't deliver because he misunderstood and miscommunicated scope -- anti-fraud, if you've been following my rants.

Their signup (all four...) are screwy and cause issues and nobody knows why. I didn't write the code, have barely even glanced through it, and it uses a third-party (Clover) that's rather screwy.

Bossman has been asking me to do various things concerning the merchant, but has never been around to provide specifics, so I'm left to guess. I've done my best, but due to the aforementioned screwiness, I really have no idea what's going on. I just sort of muddled my way through.

Bossman also asked me, super late on Friday night (after 8:30pm), to rename one of the merchants because there are two with the same name (with different Clover creds, etc.) and that's just confusing. I didn't see the message because late and tired, and he didn't follow up or text/call me until two days later (today, Sunday). I also thought these were strictly for diagnosing and were de-listed. I had no idea the merchant was live and people were actually purchasing things for it. Had I known this I would have freaked out and demanded specifics on Thursday/Friday because wtf? debugging in production? with broken merchants? selling things for real money? scary bad? hello?

Anyway, I didn't see his message until he texted me about it at like 5pm today while I was about 2 hours from my computer. He's understandably frustrated, and I totally don't blame him, but fuck, miscommunication is a serious problem in this company, and that's amazing because it's so freaking small.

But the short version is that I'm likely going to get blamed for all this, Clover screwiness included. Bossman and I set up a call for 10am tomorrow and I'm positive he's going to try pinning it on me. Totally not going to let him, but his social is lv16+ while mine's like. 2 or 3. 😕 I'll see how it goes.

Really though, I should read @rutee07's book and just roast these fuckers.

Anyone else is doing this? When you know you need to implement it, but want to fucus on something else and #TODO just doesn't cut it. xD

I FUCKING LOVE JAVASCRIPT...

Google:- Google home is using machine learning to remove all type of back noise like traffic, air, and others so the call experience goes smoother.

Microsoft:- In Skype we are using machine learning to catch all type of back noise and mix it with your voice. Skype will try every possible way to make your call experience as bad as possible. Every type of noise Trafic, Air, hardware, your breath if there is nothing! the software will cut your voice and send only a few parts.

I wrote a todo list program, which also is my first self written api. Currently load testing. Server is ok.

// TODO

Wait..., what did I have to do here?

well.. okay...

!rant

Whenever I open someone elses code, I do a project wide search for "FUCK".

Found many of these:

die("FUCK")
// fuck this
// #todo FUCK

Works on github as well. 😂🤣

Checkin into old projects be like..😵

Might be nothing for others, but I finally published my Vue website with the following setup:
1. Vue inside docker
2. Nodejs API inside docker
3. MongoDB inside docker
4. Nginx as reverse proxy
5. Let's Encrypt

6. NO I WILL NOT SHARE THE LINK, don't want to be hacked lol and it is for personal use only.

But I'd love to thank devRant members who have helped me reach this point, two months ago I was a complete noob in Vue and a beginner in NodeJs services, now I have my own todo website customized for my needs.
Thank you :)

Had the great idea to look through all the TODOS in a project, only to find this masterpiece of comment. 👏🏻

I've got a feeling that it's gonna take a long time to complete this TODO.

*sigh*

Ok, ok... calm down... 🙄

Sometimes I'm too hard on myself.

So I had to implement something which I didn't know as a part of my internship. What do you think I did?

15 hours worth video lectures in two days :x

This was my TODO list for this weekend, guess how many are left for tomorrow?

awesome wm update - after fighting with netctl + networkmanager issues, I am done, well still a lot on my todo, but that's what I am happy with for today, without having to look up more lua stuff.

btw firefox sync sucks, since neither addon nor browser settings sync

Found in repository:
<some_code> //TODO fix it, its really important
It was commited 2 years ago... and still exists in code

God dammit why does he need to test things with my account, I have work todo. Can't he just use a 'test' account.

Having trouble logging into an app I am suppose to be working on with another dev. Debugging and found this:

// TODO: Temporary Optional because the API is not working properly

... i'm not happy for so many reasons

this code is messy .. it has to be refactored..

abstact those classes to commom interfaces .. create a base class for all those common classes .. make this a parameter, make that a setting.. generalize this, pass a behaviour to that.. separate responsobilities..

hmm .. need to handle that special case .. let's just add a temp method for now to get it compiling .. //todo this later .. maybe add a couple virtual bools to handle the base class behaviour

238 compilation errors! .. let's do a static var for now on this.. and just add this for backward compatibility .. maybe hardcode that dll name, I know it'll NEVER change..

aah finally, all compiles..

oh..

this code is messy .. it has to be refactored..

The authors of these two rants are meant to be together

I wish I had a dollar for every unsolved TODO I forgot about

JustTechNerdThings #193240927340293

Having your tabs as a TODO list...

I dive in head first.

Some existing program annoys me, so I get this itch to write a selfhosted Spotify in Go, or a conky with 3D graphics in Rust.

I check the homepage of the language, download the tools, check which IDE is great for it.

Then I just start writing code, following the error corrections thrown by the IDE, doing web searches for all errors. Then when I run into a wall, I might check the reference docs or a udemy course.

Often I don't finish the project, because time is limited and I still have 4 million other things to do and learn, but at least I've learned a new language/tech.

Con: For tech which uses unique paradigms like Rust's memory management or Go's Goroutines, it can be frustrating to bash away at a problem using old assumptions.

Pro: By having a real demand for a product with requirements instead of a hello world or todo app, it's much easier to stay motivated, and you learn beyond what courses would teach you.

-- Once upon a time in a long forgotten country, a most wise wizard created a magic software that would replace all TODO comments in PHP files with actual code...

-- But dad, that's the wrong story. You wanted to tell the story of the WTF witch who makes all JS objects falsy.

Me -- Hm, okay mister, you got me. Let's see.

Me again -- Once upon a time in the far-off country of Whatthefuckia...

Man I'm so proud of my son.

Found this in my work code. This comment is from 2009.

Collaboration at it's best.

I swear to god if I see another goddamn todo list tutorial im gonna fucking switch careers. JS fanboys with their blogs... jesus christ i thought npm was spoiled but god, try googling angular tutorials... Seriously, you pick a framework and write a useless shitty blog article about the most obvious implementation? Is that your thing now? Write a tutorial on how to make a mailchimp clone? too hard? I thought so. Your mum must be very proud of you crackhead

Fuck I hate bloated app permissions but I guess todo lists that know who you most likely to chat to when taking a dump is what we get for demanding everything for free. I get why Snapchat wants so much, I just find it fucking ironic that this is from a company that founded itself on the concept of privacy 🤦‍♂️

Thanks Google

Omg I just realized there is no code highlighting here!
`// @TODO: Please add this... `

Made my first Node.js Todo list today! Got myself a new front end design tool, Bootstrap Studio (50% off). Learned about REST, using Node as an API and MongoDB and Angular! Had a lot of fun learning and I would recommend it to anyone that's a Node.js beginner. I want to do a video tutorial series on Node.js, is that a good idea?

//TODO uncomment the following line if the Product Owner change her mind again this week....

*yesterday before I took a vacation

//TODO - I will probably never do anything about it but I will Put this thing here just to make myself feel like some day I will

This is never going to happen - aka:
//TODO

Just add "TODO" there

I just did a code review on an old project of mine. 10k lines altogether. 5.7k TODO's. I can't even.

Fuck you google android IME team and fuck their open source policy..

So recently i had a chance to work with AOSP LatinIME code, basically our Android keyboard was forked from very old code base of LatinIME and my job was to change its base version to latest Version available on AOSP repository. Downloaded latest Android 8 codebase. Did 2 weeks of deep investigation of what improvements we will get from upgraded code base.

And I came to know that those Google fucking cunt sucking dick heads deprecated that project and broke the whole thing to a pice of shit. Half of the code is broken with fucked up todo stuff and motherfucking missing method implementation with not implemented warnings. What those motherfucker did is that they abandoned the open-source project after they released Google GBoard, and fucked the stable code by adding quard gram support and dictionary download with multi account features which was never completed by those motherfuckers..

Those misguiding donkey shit fuckers kept a depreciated project in AOSP build tree which has not received a single fucking commit from shitty ass Google IME team, is said to be reference model of Android IME implementation..

What kind of fucking shit is going with open-source code in name of making competition high with thirt party Android keyboard developers ..

Fucking shit fucking ime team .. fuck you .. wasted my fucking time reading your shitty code base .. Fucking shit

Long story short a guy texted me on Xing, he had an interesting idea, I joined in and now we are founding a startup.

Short story long, a guy texted me on Xing. I usually don't give a fuck because there always just fucktards that want to offer me modern enslavement. No thanks you lifeless greedy hamsters! (no offense) This time was different though. It was not the usual kind of words and the idea sounded pretty awesome. So I gave it a try.

We met in a Café and talked about the idea and about my role in it. It went pretty well and we basically had a nice little chat, coffee and cake.

I was still not convinced. It sounded to good to be true. Why would something like this ever happen to me? You know that kind of feeling. It was like "Hopefully I'm not selling my soul to the devil now."

We now work on the project, already have 5 customers and are a step before the first financial investment. I'm pretty amazed how that turned out!

Now to disappoint you a bit more (or maybe to give you hope?) All I've worked so far (except that one little one-year internship) happend by, me talking to someone that had a job, me being honest about what I want and me rejecting anything that runed my guts inside out. That's it. I never really applied for something. I just get to know the people and with that comes the opportunity. Just be respectful, curious and honest. The others will notice. Chances rise that you'll find something you love todo.

if(true)//TODO: implement later
{
//do stuff
}

Todo cought in prod

When you find a 'TODO' comment deep in a crucial function, that you know have been there for at least 5 years. :S

Daily todo list, and Pomodoro Technique

How much You know from this?
How much you are earning by that knowledge?
How much your company can give that person?

//todo: make this work.
*a month later*
//todo: what should this do?

Today we'll refactor the API.
Tomorrow we'll celebrate.

My Future Self need never know how bad it once was.

just got this from easyJet... I guess someone forgot to comment something out :D

My coworker

Reviewing code in a project, found this one:

# Todo: Fix horrible parent member check. People may have been killed for better code
-- horrible code here --

Status update after my second day of my internship:
I'm pretty good at making todo-lists.

A colleague had to show up for a demo in 10 minutes, and urgently needed to fix some CSS.

I told her the right way would take more than 10 minutes. The quick and dirty way was to add an `!important`.

I made her write a comment:
`// TODO: Fix this hack made for the demo dated blah blah`

Wow, Issues on GitHub are really a good way to maintain a descriptive TODOs for your personal project

I don't always have time to do //TODO but when I do, I still don't.

Whelp. I started making a very simple website with a single-page design, which I intended to use for managing my own personal knowledge on a particular subject matter, with some basic categorization features and a simple rich text editor for entering data. Partly as an exercise in web development, and partly due to not being happy with existing options out there. All was going well...

...and then feature creep happened. Now I have implemented support for multiple users with different access levels; user profiles; encrypted login system (and encrypted cookies that contain no sensitive data lol) and session handling according to (perceived) best practices; secure password recovery; user-management interface for admins; public, private and group-based sections with multiple categories and posts in each category that can be sorted by sort order value or drag and drop; custom user-created groups where they can give other users access to their sections; notifications; context menus for everything; post & user flagging system, moderation queue and support system; post revisions with comparison between different revisions; support for mobile devices and touch/swipe gestures to open/close menus or navigate between posts; easily extendible css themes with two different dark themes and one ugly as heck light theme; lazy loading of images in posts that won't load until you actually open them; auto-saving of posts in case of browser crash or accidental navigation away from page; plus various other small stuff like syntax highlighting for code, internal post linking, favouriting of posts, free-text filter, no-javascript mode, invitation system, secure (yeah right) image uploading, post-locking...

On my TODO-list: Comment and/or upvote system, spoiler tag, GDPR compliance (if I ever launch it haha), data-limits, a simple user action log for admins/moderators, overall improved security measures, refactor various controllers, clean up the code...

It STILL uses a single-page design, and the amount of feature requests (and bugs) added to my Trello board increases exponentially with every passing week. No other living person has seen the website yet, and at the pace I'm going, humanity will have gone through at least one major extinction event before I consider it "done" enough to show anyone.

help

Today I woke up with 2 things in my personal todo list

1. As coder, I need to figure out why my yaml parser doesn't work

2. As Lv 60 wizard, I need to clear morroc 245. Wtf with that once punch kill charge attack....

// TODO

Finish the project

// TODO: Obligatory May the 4th pun something something date formats argument

Revenge of the fifth tomorrow!

I swear to god, if I read another medium post on how you managed to be focused and productive I will fucking... well... roll my eyes, make a facepalm and rant about it on devRant!

Who gives a shit if I'm unproductive and unfocused?!

Well, look at me now, I'm fucking productive while I write about you, you fucking peace off shit! And guess what? I'm not even using any of your 40 todo apps or time trackers. There is no pomodoro timer next to me or framed quotes from Steve Jobs hanging on the wall. Oh, I must be a fucking genius!

But what if YOU became unproductive?
What will happen when YOU start to procrastinate?

Do you really think the world would care?

Oh, but you are not really a writer are you? you're a developer building your app!?
Well fuck, I guess you're going to change the world than?
It's your big project. Your life's work, your legacy.

Let me remind you...

All apps will be abandoned!
All blog post will be forgotten!
Productive people will die!
Focused people will die!
Enthusiastic bloggers writing about productivity will die!
All CEOs and CTOs will die!
All developers will die!
Steve Jobs is dead!
In x years, you and I will also be dead!

Whatever you do, it's not really that important!
It's really not.

You're not going to change the world.
The world doesn't need another app.
The world doesn't need your advice on how to be productive.
You are not special.

Deal with it!

Today, I was so certain that all the functionalities were implemented to handle some webhook calls from a third-party service. It's a script I wrote that has been running for 2+ years uninterrupted or without any issues.

We got some "complaints/notices" today that some "special" actions weren't registered, so I thought that the third-party service just didn't send those actions via their webhook. After some research I found a part where they explained that those actions trigger the webhook like any other action etc. So..

First thought: "okay, maybe they implemented that at a later stage" (was not the case)
Second thought: "maybe this is not what the client meant" (it was)
Third thought: "Then it should have been implemented" (it wasn't)

Okay, time to look at the code to see where this could get handled but apparently isn't. All the actions look good, nice, clean handeling etc, nicely documented code (gave the 'past-me' mentally a high-five)..

I scroll further down to that specific action and it was quiet obvious why it didn't work.. I just see an empty function with the comment:

"//TODO: maybe handle this action one day. don't know what this does atm, probably unused.. Will take a look at it next week.."

.. :D

I took my 'high-five' back..I just needed to copy-paste some other code and change 1-2 parameters..

//@todo: fix this shit

Joomla 2.5 is fucking hell!!
50% of the documentation us marked as "TODO" FTW

When you're still finding new

#TODO: Fix THIS!

comments...

This might not resonate with many ranters here... but FUCK Taylor Otwell & Graham Campbell.

Like, not on a personal level. Maybe they're great to drink a beer with. But as framework devs... fuck everything about them.

Laravel seems so nice, it takes away many annoyances of developing in PHP. Collections are the array object you've always needed. The route bindings, middlewares, request validation objects, it's all sweet.

But eventually your company serves a few million customers, you run into specific performance problems or missing features on a deeper level. You open the issue tracker... and see a few hundred issues about the problems you are encountering, they already exist.

Some just have a short paragraph with a request for a feature, some complete PRs with tests in the style of the framework. All of them closed.

Reasons?

"We don't think anyone will ever need this"
"This seems complicated, you can just do <super non-DRY hacky code>"

FUCK YOU WITH YOUR TODO APP SNIPPETS AND USER-POST-ARTICLE EXAMPLES. I'M NOT BUILDING THE NEXT WORDPRESS. I'M DEALING WITH THE REALITY OF GRAPH DATABASE CLUSTERS, COMPLEX AUDITING LOGS AND A GAZILLION QUERIES PER SECOND.

Sigh... the problem with all these "simple" and "elegant" languages & frameworks is that they don't fucking scale.

Not because the language, server or framework intrinsically can't do it, but because the maintainers are stuck thinking in terms of their retarded non-realistic example apps.

I think I'll go back to my cave and write some Haskell or Rust to calm down.

That moment when you edit the Todo list for your personal project, add a bunch of ideas and the proceed in procastinating like you did before and feel _very_ productive about it.

Is it legal to destroy other company's site or app. because they didn't pay your money in the past?
and also app they created is not secure.
The company is in another country.
.
.
.
If "No"
I'll still do that. I don't care.

Tell PM that something isn't possible. Still puts in the todo list with high priority...

i told my boss ill just do it tomorrow and he agreed and i never did it. i still have it that part of the code as a pending TODO. it has been 7 months now.

if(night){
sleep(12*60*1000);
}else{
//TODO update when you get a job
sleep(12*60*1000);
}

Yesterday I planned out the next large feature in my app. Created all necessary classes and methods. I didn't however actually code it and instead added //TODO: s to all the functions. I checked how many there were. It was 57 todo's. Went afk. Doing that this week.

Using post-it notes for todo lists and never look back at them.

If only my deadlines grew as fast as my todo list does...

At work, all errors within the site are logged into our database with a subject and error column. SQL errors are logged in the subject field while the traceback is put in the error column. However, a lot of SQL errors are really large and exceed the max character width of the subject field, causing yet another SQL error, and the cycle repeats. This recursive error has been the bane of my existence, because 1) it times my local dev instance out and 2) the error doesn't end up getting logged because the server both freezes and the error can't be inserted in the database. You can't even begin to imagine how many hours I've wasted trying to find what line I changed cause total and utter failure with absolutely 0 error logging. Next thing on my todo list is to fix this fucking issue since the head dev refuses to get it done.

Hi everyone,
I got an hardware question. Im planning on getting a personal home server. I want to use it as a small gitlab server, continues integration, and the like for personal projects.
It has to be power efficient otherwise my dad will start crying.
I want it to be relatively cheap and running linux.
Ive got no clue what the best thing todo is. Should I get a prebuild one or build one myself.
For prebuild ones, what brands should I look at?
For a custom built what hardware do you recommend me?

// TODO Wish happy year to devranters

Found this comment in a class I visited today after a few months of writing it.

//todo: Fix this fucking POS hack

I have no idea what POS refers to anymore. FML.

//TODO: make sure to add test case later

How surprising is it when a person designs code in a very clear and impressive structure and just when you think about asking them for guidance, they reveal themselves to be complete turds?

I've been working with this person's "infra" code, at work. I've rewritten some classes to use their infra. I had a vague idea of how the classes work. I had no idea of how their code works. Expectedly, there were some issues but now only minor ones remain.
I asked them for a description of what I'm supposed to do for the few bugs I'm facing. They replied in such a condescending tone, it made me want to punch them through the screen.
Almost a month later, we're still going back and forth with emails. I've been swallowing it and responding calmly. I never got direct answers. Always deflections to irrelevant things or veiled insults. I took it because they did correct one silly error of mine that actually my code reviewer should've caught. (What's worse is that it got introduced by me just before my review and commit.)
But does that give them the right to insult me in front of the whole team including my project manager? I got a reply today from them with everyone of note in cc implying very clearly that I have not done any work. They highlighted a line from my code with some todo tag (that was not meant for them) to make their invalid point. A line that's unrelated to the bug I asked them about. This is after I proved them wrong when they insisted that I had done something wrong about a feature related to the bug.

If you don't understand what I asked for fucking ask me to ask again. But do not fucking try establish yourself on higher ground by pointing out irrelevant things in my code.
I was shocked and enraged that they'd do such a thing. I double checked everything like a mad man. Despite knowing that the fix has to come from them, I was instantly transported to the noob stage, grasping at straws. I wanted to send a really scathing reply right away but my manager asked me to wait.

My mind is now a see saw shifting between a panicked noob questioning every fucking thing I ever did in my nada life and a hungry enraged monster looking to maul that fucking shithead for burning me like that.

The best/worst code comments you have ever seen?

Mine:

//Upload didn't work, have to react:
system.println('no result');

//$Message gives out a message in the compiler log.
{$Message Hint 'Feed the cat'}

//Not really needed

//Closed source - Why even comments?

//Looks like bullshit, but it has to be done this way.

//This one's really fucked up.

//If it crashes, click again.

asm JMP START end; //because no goto XP

catch {
//shit happens
}

//OMG!!! And this works???

asm
...
mov [0], 0 //uh, maybe there is a better way of throw an exception
...
mov [0], 0 //still a strange way to notify of an error

// this makes it exiting -- in other words: unstable !!!!!

//Paranoic - can't happen, but I trust no one.

else {
//please no -.-
sleep(0);
}

//wuppdi

for (int i = random(500); i < 1000 + random(500 + random(250)); i++)
{
// Do crap, so its harder to decompile
}

//This job would be great if it wasn't for the f**king customers.

//TODO: place this peace of code somewhere else...

// Beware of bugs in the code above; I have only proved it correct, not tried it.

{$IFDEF VER93}
//Good luck
{$DEFINE VER9x}
{$ENDIF}

//THIS SHIT IS LEAKING! SOMEONE FIX IT! :)

/* no comment */

Today, i discovered thus beauty within our legacy code:

// TODO: this is probably the most dirty thing in our product. It needs a model more than anything else

This captions a crappy part of controller code for several years :/

I guess TODO is used so often that atom just recognizes it as a keyword...
Not getting stuff done is super popular!

EVERY-SINGLE-FUCKING-DAY.

Usually when I sent e-mails/messages with complete instructions for a client and then I receive this as reply:

"Ok, I did step one, what do I do now?"

I often reply with a "look at your message history" and, yet, I have to re-send everything again because of their inability todo so (or their laziness for searches).

😰

Target: Migration of an old system(not developed by us) to a new without touching existing applications.

Todo list:
[✅] Migrating old webservice from VB.NET to C#.
[✅] Decide if we go to the old system or the new based on the document class.
[✅] Start implementing same logic to the new system so the results will be the same.
[✅] Stunble across a search method with fuck up logic.
[✅] Create test cases to foresee all cases.
[✅] Implement logic for new system.
[✅] Stuck in infinite refactoring to fix existing bugs brougth from the old code to the new while mantaining the response the same.
[ ] Become insane during the process. (In Progress)

Walking in a shop. Using my react native todo app with redux i made for personal product. Feels good man

There are few developer who name their functions all wrong, but the functionality is fine. Then there comes those who name their functions right but the functionality is nothing close to what it says. There is this function I debugged. It's name is optimizeQuery. It does not optimize the query at all. Rather dismantles it. Also it made it's way to the production. 😅 Now I have to correct and optimize the optimizeQuery.

I have the habit of adding //todo comments to my code whenever I need to implement something later. Very useful to just search your code for "todo" and see what is left to do.

That is all very well, but I just searched my project for "todo" and there are SO MANY //todo comments in the third party dependencies...

//TODO: Write a really awesome rant that people relate to and upvote many times

// todo: WHY THE FUCK ISN'T WORKING ?????

Making todo app on it 🤷🏼‍♂️

Hello fellow developers!

I know this is devRant, but I don't know of a better community with such diversity of developers like you guys and I need your input.

I decided to go on a language journey. I come from a background of php/javascript and feel the need to expand my horizons.

I'm going to write the same app in each language to get the feel of it and become familiar with the syntax and language concepts.

Since I'm a web developer I'll focus mainly on languages used on the web like: Java, Python, Ruby, etc.. But I want to cover others as well, like Objective-C/Swift, C++/C#.

I'm having trouble figuring out what kind of an app would cover most of the ground. I know the basic guideline for this is a TODO app for web frameworks, but I
don't feel like writing a TODO in Swift or C# really cover what the languages are intended for.

I don't know enough about the environments yet to come up with a good idea.

I want something, that can be language independent but would utilize the power of each language in one part or another and is still simple enough not to require weeks of development.

Does anyone have a brilliant idea what that could be?

When you like your framework but had enough of the legacy project's recoding in it for the week

ECMAScript is everywhere, so I thought: Let's do even more inappropriate and insane things with it ;)

...Like using Duktape (small ECMAScript engine) and exposing LoadLibrary/GetProcAddress along with some helper routines to describe the routine's argument types and return type, and finally providing a routine to invoke those routines.

It's a very rough prototype that can handle up to 4 arguments in a 64-bit Windows environment.

Next "todo" is structure handling which will initially be a case of stuffing data into a Buffer() object.

I'm not sure what exactly I'm trying to do with it or why...

Stop commenting out code blocks!

Either fix your shit or delete it.

I am open to argue what fixing may mean, as it is perfectly fine to make your broken code not reachable, e.g. via feature flags or skipping certain tests. Yet never ever should you comment those blocks!

So you say you want to keep it for historic reasons? You know, that is why we use version control! If you ever need certain functionality back, you can restore that state.

Each decent IDE also offers a local history where you can even restore code blocks that weren't even pushed or committed. So use that!

Commenting out test cases is a really bad habit, as you have no reminder that you shall restore it.

And no, a TODO and a FIXME won't count as a reminder as you have to actively look for them. And we all know how well that goes, don't we? (One time, I found a typo of a `TDO`. So even with a regular lookup for TODO, stuff will slip.)

Each test suite offers you ways to skip tests if there are valid reasons why they should not fail the build temporary and they offer colorful feedback. Yes, that means that your tests won't be green, but guess what: That's a feature! They shouldn't be.

That yellow is a fine reminder, aka warning!, that you should really fix your shit.

Commented code screams: "I DON'T KNOW WHAT I WAS DOING!" and it confuses the hell out of other developers ("Was this commented because of debugging purposes and should be active again or can I safely delete this!?") and adds verbose crap to the code base.

If you find yourself to be in a place that you comment code a lot, I also argue that your workflow is broken.

When you are using a decent debugger, there shouldn't that much of a need to comment in and out a lot of code in order to reason about your code-base.

Anyone else have 100 .txt files on the computer called note(54).txt? Or TODO(32).txt? Yeah... Someday I will compress them into one so I don't miss something important for work. Why don't we have issue tracking?!?!

I am so bored right now i decided to make a C++ wrapper of the API, i dont know if there is already is, but i have nothing better todo anyway.

Interesting mini algorithm and data structure projects ideas that can do the wow effect? Some on my todo and have done lists:

- Hash map, hash table and hash set in C

- Visualize path finding algorithms like A*, Djikstra, Bellman Ford, etc.

- Encryption algorithms like DES, AES, Blowfish, twofish, etc.

- Efficient webcrawler in java

- Efficient chess engine with bitboard

- Wikipedia article crawler

- Convert any photo/video in an Ascii formatted photo/video

- Floke simulation with extern enviroment

- An Identicon generator

I would love to hear more ideas of you guys

Famous developer sentences #1:
"I leave it like that for now and refactor it later"
It will definitely never going to happen! ;)

Can't come up with ideas right now? Do you feel dull and without energy?

Write a Thesis! The ideas will start to overflow as if there is not enough memory to hold them. Promise.*

Buy now for only 1337 $ 💵

*does not apply to the topic of the thesis though

Readme.md
*Todo: Add description*

>103 commits
>Last commit: a year ago
>Last commit on readme: 5 years ago

Slothful cunt, you don't deserve these 7 stars

Best part of being a developer...

let you = {
developer: true,
coffee: 9001,
sweatpantsOn: true,
makeCoolShit: function() {
// TODO: make cool shit here
}
};

while(you.coffee > 9000 && you.developer && you.sweatpantsOn) {
you.makeCoolShit();
}