If you had
one language
One framework
To code everything you want
Would you learn it or let it pass

His code is heavy,
arms are weak,
mind is bending.
It's all spaghetti.
He is nervous but looks calm and ready
to go now
but he keeps on forgetting
what he wrote down.
The manager is getting loud
He moves his mouse but the bugs won't got out
They are features now
Time to ship
Over blaow!

Received "emergency update" code from internal enterprise security team. Wasn't given time to do code review; was assured code was reviewed and solid.

Pushed code to over 6k lower-level servers before finding this gem buried deep within:
...
cd /foo; rm -rf *; cd /
...

(This ran as root, and yes, the cwd was / from earlier in the code).

/foo, of course, did not exist on some servers.

Now, it is those servers which do not exist.

FML

Just saw an ad:

"I learned to code in 2 months thanks to X School and now I'm working at Google!"

Seems like now is the right time to dump your Google stocks.

Boss throwing up a huge source code that I didn't see before.

Boss: Hey, this is an app from a contractor to do XYZ.

Me: Oh, okay.. so?

Boss: You will continue the code and the maintenance now. How much time do you need to implement X feature?

Me: I need to see the code first, can't say nothing now.

Boss: ok I need estimation now.

Me: *getting nervous* I need to see the fuckening code first. if you want estimation now I would say one year..

Boss: what?

Me: what?

GF: I swear, you're spending more time staring at the screen than actually typing anything.
ME: Because literally 80% of coding is staring at the screen thinking about how to code something. My mind is an endless void of possible approaches to a problem.

Every fkn 3 to 4 days, some random dev shows up in my office really really fkn confused and frustrated about something he doesn't understand - because I have a dark secret.

Sometime, in cold lonely nights, when no one is watching, I write my documentation before the actual code.

Somehow, sometimes documentation without code attached to it makes it to production.

Today someone yelled at me for wasting his time because he wasted 3 hours trying to find the code the documentation belongs to - and demented I stop the practice from now on.

Agh.

PHP 🐘 is so damn easy to learn, run straighforward in all OSs, that anyone can start coding in no time. Therefore, the amount of crap code around, made by unskilled devs, is just *unbelievable*. 💩

Had a PR blocked yesterday. Oh god, have I introduced a memory leak? Have I not added unit tests? Is there a bug? What horrible thing have I unknowingly done?

... added comments to some code.

Yep apparently “our code needs to be readable without comments, please remove them”.

Time to move on, no signs of intelligent life here.

So today this Mother F**ker get HR to back him up to accuse me of not communicating well in the team because I consistently asked him (the code owner) why he kept coding not following the coding guideline.

How is it not communicating? He literally ghosted me and blocked me every time I ask him questions. Which I somewhat don't understand what he is trying to do. HR lady told me that a senior software engineer should have the knowledge to understand everything and all the code.

But the code looks like this :

And when I was busy wasting my time on my girlfriend who is my ex now, my friends were busy coding an AI chat-bot. Now, I use their chat-bot to talk to when lonely.

Moral :
Girlfriends ditch you.... code doesn't. Love code.

On a serious note, most developers really don’t code complex algorithms all the time. The bar for interviews is way too high— to the point that most people get discouraged from pursuing a career in IT.

If you are copy pasting code from somewhere else, spend some time and effort to understand what that piece of code is actually doing, and how much of your requirement does it satisfy.

Advice that I give to interns/grads:

In uni/college, you're taught *how* to code something to achieve a goal, and 99% of the time the code will work and do the job in a lab.

But when building things for a real production environment, you learn the 100 ways how *not* to code, from seeing things break left right and centre - basically everything and anything can break your code, whether it is users, the OS, other people's code, legacy code, lag, concurrency, the alignment of the moon to your server...

Senior architect-type person at work wants me to review some code he's written. Is it on GitHub/Gitlab/Bitbucket etc? Nope. "Here, I've printed it out for you. " 😂

When was the last time you printed code out? Also it's in black and white, times new roman😱💀

Reviewing coworker's code:

Me: I see you're doing a convoluted sort for every element twice to get your two lists in sync... 😐
CoWorker: Yeah. *straight face, no regrets* That's the only way to do this.
Me:... Uh... No? You can just manage one list with a simple struct and then use the the standard sort.
Coworker: Yeah sure I know. But it'll take time. We don't have time.
Me: *aghast* This is embarrassingly bad code!
Coworker: Don't worry, later on I'll use a hashmap for it. But this needs to be pushed now.
Me: *to myself, no you don't need a hashmap*
Okay, you do you but I can't back you on this. It isn't going to take a lot of time to correct it.

Next day.
Coworker: Hey can you review my code again?
Me: You've made the changes already? *in a bored tone, knowing that they wouldn't have changed shit*
Coworker: No this is a different file. Our manager agrees that we can worry about performance later.
Me: Sure. *😀🔨🔨*

Few weeks pass by:
QA: The operation takes absurdly long time to complete even with the smallest data. Ten minutes for X is unacceptable.
Me: Who would've known? ☺️

Adult responsibilities for the morning are complete. Trash is out, dishes are done, coffee is made, time to learn some code ya filthy animals

Just downloaded some big ass codebase and the first line i read is:

"// The source code is not well documented, but every advanced programmer will be able to understand it after some time."

Well... let's find out about your definition of "some time", Dickhead!

It's disheartening to see a senior member of my team shitting on the code of less mature developers. Don't just say "this is unacceptable", elaborate, teach them. How are they going to action anything from that feedback?

Take the time to respond to their questions when they ask for clarification on what you're saying. Don't berate them.

Honestly some developers need to learn a thing or two about code etiquette.

There's no room for good cop / bad cop behaviour.

My Boss: When are you going to finish?

Me: There is a bug, I'm solving it, I need more time.

My Boss: Why have you introduced a bug in your code and now solving it? It were more simple if you didn't created any bug!

Me: WTF!!!

That time when you code up something really cool (to you, that is...) and none of your friends understand.

Me: "Look at this cool thing!"
Them: "Looks like a bunch of numbers."
Me: "But they mean foo, bar, and baz!"
Them: "Whatever."

:(

DevRant is cool, mostly because we are united. We don't agree on OS, language, theme, or tabs. But we are united by code. Next time you want to troll someone, think about why you became a developer. To Code.

Dude, for the hundredth time, stop leaving random chunks of commented out code all over the place in case we "need to find it easily later"...

This is literally the reason we use git.

No, I will not pass it in a code review. The same as last time. And the time before...

Dahhhhh

Senior: I've been programming for a long time. I know JavaScript.

Me to myself: I've seen your code, it is shit.

Senior: (builds JSON with string concatination)

Me to myself: ...

What am I to do? The system is full of stuff like this, and minimal support from management to fix and rewrite.

The worst feeling is writing so many lines of code knowing you could do it in a more concise way if you just had time to think about it but you don't.

*writes code in 10 minutes*
"Time to debug this"
*debugging?*
*starts to feel hungry*
"How late is it?"
*2 hours have passed*
"Wtf"

Boss: I wrote some tests and there is a bug in your code but I cannot find it. Fix it
Me: Sure. I'm on it.

Narrator: 5 minutes later

Me: Boss, I found the bug. It's in your testcode...

Seriously... WTF?!

(before someone suggests that my code should handle all test cases... He tried to measure the time the program needed to response and fucked it up...)

My computer science teacher is very sly: while you are working he stands right behind you for some time, so you start writing good code, functions for everything, perfect indentation... But you don't know if he is still behind you, and you're not brave enough to look back, so you write good code for the rest of the lesson.
What a good prof

{Context: English is not my native language}

The first time my code get a review ( by my boss that time)

Boss: Your code is full of butts 🍑

Me: Eh, What?

Boss: *showing his screen* see that? variables names: validateButt, contactButt, seeMoreButt..

Me: *interrupting him* oh, I mean button.

Boss: I know, just being sarcastic, but it'll be better to get another suffix.

Me: 😐

Just my $.02:

One thing I think a lot of students/schools miss when learning/teaching, is that your code has to be *maintainable*. Your code is (hopefully) going to be used for a long time, so program it to make it not only easy to upgrade and maintain, but easy for SOMEONE ELSE to upgrade and maintain, too.

The best code to work with is the stuff that's been coded with maintainability in mind.

Senior Engineer -
Hey. I have a code that hits API to get details and multithreading is implemented. Can you just change the URL formed to hit Api?

Me
Yeah sure why not.

Me
After some time I discover that the initial code itself wasn't working 😐
I realise i need to fix code, fix multithreading and then make the URL changes.

Just finished......Realised had to rant....

I have never written a single unit test in my life. Hence my code breaks from time to time. Karma is a bitch 🤣

To paraphrase Jeff Atwood: everything you write sucks. The goal of programming is not to write great code, but to writes code that sucks less each time you write code.

I am sure this has happened to all of us in some extent with some variations.

Colleague not writing comments on code.
Ask him something like "How am I suppose understand that piece of garbage you have written when there is no comments or documentation?"
This keeps happening for a long time. Some time after, I write a kernel module using idiomatic C and ASM blocks for optimizations (for some RTOS) and purposely not write neither documentation nor comments.
When he asked for an explanation, I answered to everything he questioned as general as I could for "that trivial piece of code".
After that he always documents his code!
Win! 🏆

Here's a conversation I had at work:

Me: "this project that I've inherited, aside from the UI problems it has, it also has severe code problems that need to be fixed"

Project Manager: "I don't care about the code. The code is not my concern. Don't waste time on it and just make the app look good."

My son is taking a nap and you know what that means - time to write some code!

Yesterday, I decided to rewrite the code of a project I'm doing for a week. I rewrote all the code with a better agility (is it the good word? ) and I ran it. It worked the first time! It worked the first tiiiiime!

If you've spent time learning how to code and you're daydreaming about having a dev job but don't have one because you're too nervous to apply, just do it. The worst thing that can happen is that you'll get the job (and be stuck ranting like us).

One thing I learnt after over two years of working as a programmer is that sometimes making your code DRY is less important than making your code readable, ESPECIALLY if you're working on a shared codebase. All those abstractions and metaprogramming may look good in your eyes, but might cause your teammates their coding time because they need to parse your mini-framework. So code wisely and choose the best approach that works FOR YOUR TEAM.

The worst part about having a job that is not related to programming is that I don't have as much time to code as I would like to :(

My colleague unknowingly uses the word "paralyze" for "parallelize". When is the good time to correctly him? So far he has successfully paralyzed my code.

Being a good developer is knowing how to balance writing perfect code with getting shit done. Working lean means half your stuff in going to die anyway, so fighting for the corpse just wastes everybody's time

Sometimes dirty code is more efficient than clean code.

If features get dropped frequently and requirements change every few days, writing best-practices, tested code is wasted time. Learned that in my first job where I thought the other devs were all bad. Until I realized their bad code pays my salary, and my clean code takes more time to develop.

A coworker that is producing incredibly bad code and refuses to learn new stuff was declared "senior developer" by my boss. And me with over 20y experience? I am just a junior.. and have to clean up his mess all the time. I guess it is time to find new job.

I HATE SVN! >:v v:< >:v v:< :@

I used to use git for my personal code repositories and for my work. In the office I moved on, they use Subversion. I’ve been using it for months, but it’s a pain in the ass :/

We use TortoiseSVN to pull code repositories, and the AnhkSVN for Visual Studio Plugin. It works fine until two or more of us have to work at the same code project at the same time.

Last week we had a very VERY urgent code to release. We had 4 days to finish it (from thursday to sunday, tests included). We had few changes to do, but the problem was that, when one dev commited something, my changes disappeared, and viceversa. The worst part was that my partners and I had to re-work a lot of bugs that we had already fixed! >:v

This is not the first time this happens :/

The worst thing is that we cannot change our repository system because we don’t have time :(

Is there any advice you, SVN users, can give us?

devrant(dot)com/rants/8848492/welp-time-to-ditch-devrant-i-dont-mind-green-dots-posting-the-same-things-over-a
This is over an actual request for development help vis a vis an actual opensource project with decades of code developments allready-in-place. That's what is causing you to melt the fuck down.

Stop taking the estrogen.

>NOOOO, ATTEMPT TO CONNECT WITH DEVELOPERS?

>NOO THIS IS ONLY A TRANS FAGGOT HIDEAWAY, NOT FOR ACTUALY PROGRAMMING!!!

>NOO THEY POSTED THE CODE? NOOOOOOOOO
@hitko

Me: *rewrites chunk of code*
"Time to test this baby. This is gonna fail spectacularly"
Code: *works*
Me: "Fuck!"

Client:
This has to be done with in 160 hours.
Me:
Seems doable

After maybe 100 hours of developing:
Client:
This is great and all but we decided to change the specs little (a lot) surely you can code this whole thing again in the rest of the time.

* Calls themselves "Software Engineer"
* Doesn't know what a thread is.

I swear these coding boot camps are churning out code monkeys whose real skill is building shitty React apps.

I believe a CS degree is necessary if you want to work on something more than CRUD applications.

Nothing against devs without degrees, but at least make an effort because my head will explode next time I have to explain to someone what a thread is and why it's a very bad idea to run blocking code on the main thread.

Me seriously debugging someone's code.Analysing the code for 15 minutes.I reach end of file and I encounter a comment saying that this file is not being used and he doesn't have time to remove it!

Incase you wonder where I am gone to: Well. Looks like I'm a part time irganist now xD

Yes, this is me,
Yes, this is very fun,
Yes, I deliberately go to church X)

(I still code a lot)

I had a coworker that was a real asshole. I noticed that often, during git merges, he removed part of the code I wrote.
So I had to spend a lot of time copying and pasting my code from git history in order to restore it.
I complained about that but he answered it happened by mistake. In reality that happened so often that he had to done it deliberately.

Btw, I did a little revenge. One day I discovered he didn't feel very comfortable using recursion. Thereafter, every time I needed a small loop I created a recursive function doing the same thing.

Fortunately, after some months I found a better job. I hope he is still debugging that code.

FML, I hate projects where managers (and other developers, too!) irrationally think that the only thing to do in the codebase is delivering new features and fulfilling change requests.

After 5 years of such approach, the code is bloated, and has hack-on-hack done against the original architecture, and management complains on the time to delivery a change, however asking them to get some time to "refactor" meets a deny every single fucking time because "we don't have budget".

Decided to leave the team. Any reason to stay there longer?

While I was in university, I used to be a good programmer (which I still am :D ), my friends used to copy my code for the assignments. One day, the teacher (one of my my mentors) called me in his office and said, "this is your code".
I'm like, in my mind, "How did he know this?"
The teacher said, "If you let others copy your code one more time, I will fail you".
I nodded my head in affirmation.
Later I understood that I've been a "Clean code" principle follower even before I knew this term. So, it was pretty easy to differentiate my codes from my friends. The teacher is really a genius ^_^

Devs : Lets pick library X, it is well know piece of open source technology, actively maintained by community for over 10 years.
Architect : NAH, it is an overkill to use it in our project , lets build our own solution.
*2 Months later*
The code base is hundreds of thousands lines of code, we basically started to look at library X on GitHub to copy features or get inspiration from that code. In that time we delivered 0 business value, it is horrible to use it and we constantly adding something or bugfixing because no one thought about something in first place.

The freaking furniture people didn't complete things on time and our business development department is still not finished. The freaking reception desk is not there yet.

Here I am going to my new office on Saturday morning. Not to code but to monitor those guys to get things done by today.

My development process seems to go:

1. Write code
2. Believe that said code is amazing
3. Write more code
4. Revisit earlier code and start to doubt it's amazing-ness
5. Get frustrated that it could be done better
6. Redo 1 and repeat cycle

Seems a massive waste of time but I tend to like taking a different approach as soon as I find I'm getting stuck with the previous one.

I then get encouraged to take the quick/easy approach which seems like a backwards step and not worthwhile because I know it won't be as fast/efficient.

To incentivise myself to get fit, I decided to do push-ups/sit-ups whilst my code compiles

All that happened though is I now spend a lot more time making sure my code compiles quickly 😅

When was last time you had Fight or Argument(restricted only to texting) with your GF/BF/Spouse while coding?

The amount of text typed on phone is more than the code on screen.

-= Me in the zone hacking out code during meeting with customer for an emergency change =-

-ready to deploy just need to....-

Me to myself:

"Oh ... oh shit ... I forgot who the customer is / who this is for / what time it is ... how do I ask these people on the call who the fuck they even are....?"

(｀_´)ゞ

So I'm a perfectionist, especially when with code, smells, solid, design patterns, naming conventions, etc and I be have this co-worker that blackmails me every time he doesn't want to do something saying "I don't know it so my code is gonna be ugly".

I’ve just received my Potato Pirate game ! Time to teach my matey how to code ! And the nice Kickstarter gift is perfect for my screen at work ;)

Wrote some code that solved a program in a semi unique way for the codebase. As in not oft used functionality of language.

Some time later... This might be hard to understand. Maybe I should do a different way.

Some time later... No, I will leave a comment to describe what is going on.

Some time later... That comment is kind of cryptic. Maybe should rethink.

Some time later... No, if the next dev doesn't know how this works then they should learn how it works. (reasoning here is that the functionality requires a knowledge of internals of language)

Some time later... Also, if nobody else gets this then they have to ask me how it works. Job security?

Some time later... STOP THINKING ABOUT THIS CODE AND MOVE ON!

The weekend is here!!!
Time to go out and have fun!!!

Nah just joking. Time to write some quality code after cleaning our company's backend (pun definitely intended) all week!

Tired of reading spaghetti code written by your team mates?

Sit right next to them and ask them to write unit tests for that code.

Smash their head on the keyboard everytime they have to think longer than 10 seconds on how to test a specific logic.

Strangle them with any wire you find nearby till they agree to break up that spaghetti code unless they already started within that 10 second time frame.

When the exercise ends, tell them this is what refactoring is and ask them to pass on the knowledge.

Being so busy that there is no time to code 😭

My time in devRant is the time it takes for code to build and deploy. devRant is why I don't improve code performance 😎

Everyone is on their vacation and I am in good mood so time to refactor some 3 year old frontend, angular, javascript code. After 5 minutes of looking, some great quality of code snippet on the image below.

You've got to be a masochist to be a javascript/typescript developer.

Each time I come back to the npm-related parts of my project, the application won't start because of some dependencies nonsense. And I know for sure I left the project working perfectly last time.

Every time... every fucking time! Just leave the project unattended for a week and be sure you'll find it dead next time.

I mean I as a developer don't really have to do ANYTHING for my code to break.

How can people love javascript is a mystery to me.

The best time to code is after 11 at night.

!rant
First time in my life I can't wait to get home to code. This is exciting! 😊😊😊

Forgot my laptop charger in the hotel, flight leaves in 10 minutes, and my computer is at 2% battery life.

I just need to build this code and push! Will the code be pushed in time? Stay tuned to find out!!

... nah jk it just died. 😧

Don't scroll here.
Go and live a real life,
Don't make a computer screen as your world,
there is a beautiful world outside of your cave,
Talk with people's face to face,
go
go
go.

Ok enough philosophy, Time to add new shit in current shitty code.
(-_-)

Ok so my pc is running again.
Time to put some Marilyn Manson on while I code.

Oh wait, what's that? Can't play music? For the 5th time today, fuck you Microsoft.

I have a lab at uni where my lab group have to refactor some code from an open source project. We got assigned some Apache project and jfc that code is a mess. Little to no documentation, hard to navigate, tests that you have no idea what it's testing, and so on. On top of that the teacher expects us to spend more time than we have on it. I'll be glad when this course is over :))

After a developer writes a 1000 lines of code with no unit tests then it is time to go home.

1 am, wide awake,
I want to go code but cannot take,
for time is not my friend,
If I go now, it will not end.
Rest is needed, sleep must be,
or tomorrow I will pay the fee,
concentration will be sparse,
and boss will surely kick my arse.

HELL WEEK is coming!! they are going to make us code IN PAPER again.... no compilers, no way to check for errors, time to die again

Gj Mastercard! My card just got blocked because every time I want pay and 3D secure code is needed, every first SMS that day is delayed by 5 minutes so session expires and I have to try again...now it happened quite a few times and card got blocked. Fucking shit...

I am an intern getting paid $25/hour for fullstack web development. Their brand new full time frontend web developer, getting paid at least $75,000/yr, just wrote these lines of code:

if(this.ackBy !== null && this.ackTime !== null)
this.acknowledged = true;
else
this.acknowledged = false;

This. Is. Far. From. His. Worst. Code. This isn't even surprising to me. How does this incompetence find work in this field

I’ve started at a new place - the team use Trello to share code 😳They are happy to zip a folder, upload and download each time a project is updated.

I’ve tried to sell the benefits of Git however some have such conviction that it would be worse. FML.

I did mostly Java and JavaScript coding before I came to my current job. When I started I pretty much had to learn PHP on the fly. Pretty much no problems, but my greatest shame from the few years I've been writing code is when I spent over an hour debugging an unknown error, after which time a fellow dev looked at my code and informed me that PHP uses . instead of + to concatenate strings...

It feels like no matter what i fucking try at this point, the universe is doing everything in its power to stop me from succeeding.............. I got so fucking depressed that i am literally writing code and crying in the same time.........

Docker I don't have time for your bullshit tonight!

You're supposed to be this safe space where my code runs and neither the code or the god damn container changed.

Don't give me some bullshit about the container either, it's pretty clear docker itself is fucked ...

Think twice code Once, if I had a cent for every time I've jump right into the code without a proper analysis or design just to notice that my whole implementation is not functional or scalable I'd be a millionare

So I just recently joined stackoverflow. Spent some time time and decided I should log out considering I logged in at work. Could not find the fucking logout/sign out button. Even after googling. Had to go to the source code and find the logout link which is hidden in the page.

Looks like it's the new vim.

So before the Age of JavaScript, when programming was trying to be an engineering discipline, I felt like we were getting close to figuring out what worked and what didn't. We had rules of thumb (more general than Patterns) and code smells.
Then JavaScript came in and no one had time to think about "engineering" anymore. I'm fine with MVP and small iterations, but the disdain I see for making code clean and extendable and improvable is baffling (and annoying). First-time coders might never have had to fix someone else's code, but two weeks in a chair should have fixed that.
It's not that understanding code is so hard (although it can be); understanding the _intent_ is hard. This MVP is great, but when no one had time to document what is actually supposed to happen, programmers have to reverse-engineer the *design*.

The feeling when you realize some people on the project are writing legacy code from scratch. Apparently it seems they've never heard of any coding standards, they think clean code and style guidelines are for the weak and single responsibility means one single method is responsible for a bunch of unbelievably diverse things. They are like the Gumbys of the dev realm but it's my brain that hurts every time I have to deal with their code.

Parts of the code I am working on date back to the early nineties, written in ancient C++ with lots of special cases for ancient compilers by people with 0-2 years of coding experience.
My favourite coding moment is every time when after refactoring a part of the code, it has about 1000 lines less (no exaggeration), is more reliable, AND can do a lot more than before.

Spent 5 hours working on a solution for a hash difficulty comparison/scaling algorithm. after a bunch of different iterations and approaches, I find that my problem can be solved by the attached equation. Its such a simple answer but no way in hell would you be able to discern the amount of time and brainpower that was put into it. The git commit is literally 10 lines of code total, but I guess its not about the amount of code, but the time spent thinking about it thay counts?

How I feel when im asked to add functionality to a project that was built like 10+ years ago and needs refactored in its entirety but the code base is so terrible that youre honestly better off just starting it from scratch but you are thrown into 5 other million things and there is no time to do it so you just shit out the bare minimum code that will not break the rest of the application.

Is it normal for seniors to talk to juniors with disrespect if they made something wrong in code?
this is my first time job ever and I feel like this behavior is so weird honestly.

OMFG!! My computer rebooted.. after VS is again performing voodoo stuff on my code..can you please fucking stop reformatting everything!? OMG it's driving me crazy, I've already disabled every format option I could find.. you piss me off one more time, I'm switching to np++!!!!

For the last time, SLOC is not a measure of anything.
Have too many, the code probably isn't DRY.
Have too few, you probably don't follow a style guide and have 120 char lines because you invented "oneliners" which you were so proud of that you had to put it in there.
Have just the right amount, and the code likely suffers from both of these at the same time.

The scary thing about burnout is that you usually don't realize you are burning out before it's too late.

Personally, at least, I've worked on projects that just felt a little intense at the time, but after taking a step back due to holidays or hitting some milestone I realize I never want to have anything to do with it ever again. One project makes my stomach drop even today every time I see the code; Not because the code is bad, but how it takes me back to how miserable I was without admitting it to myself.

The biggest red flag I look for is when I'm tempted to work on stuff in my free time. When this starts seeming like a solution there's a serious problem with the project that needs to be addressed.

Imagine updating a legacy web app and the code is so bad it physically makes you sick every time you look at it. Tables with over 400 columns, . And don't even get me started on the security issues. Apparently writing "Confidential" on the top of the page is enough security. And that's just the tip of the iceberg. People should get licenced before being allowed to code.

Can anyone tell me why is it good to use some crap language that transpiles to javascript? Yes i hate js too but 90% of my time using reason/ts/elm is just

>ddg how to do x in y
>no answer
>Js.unsafe.eval "js code"

Like???? None of them is a 100% complete wrapper???

Leo Moracchioli
Coffee
Intellij IDEA Ultimate (Distraction free mode)

Stepping into heaven ...

Is it worth to learn vim? I mostly write code in JS and currently using VSCode so I wonder if it is worth spending the time to learn how to properly use vim

What is your Favorite time to code ?

If I had to audit my current code I'd definitly stick a cactus up my arse shouting in the mirror:

ALL YOUR CODE IS GOOD FOR IS ULTIMATE DELETION. YOU FILTHY MAGGOT! LEARN TO CODE... *rage quit*

Really, coding shit because of spare time simply makes me ripping my face of 💀

I have a lead developer who is obsessed with over-engineering everything to the point where we are adding features that he thinks the clients will ask for, but 50% of the time they don’t want it and we just end up maintaining useless code. To top it off, he doesn’t touch the code anymore and is a glorified business analyst, plus he’s slated to retire soon but keeps pushing the date back a year at a time. Just move on with it! I want to be spending my time on cleaning up technical debt, not making more.

Migrating to another sub domain for the 4th time.
First they say 'oh this sub domain is just for demo and you can freely test your code on it .
Few days later they say the same thing to another team and then :

- 'dude ! Is the website down because of your code ?'

- 'The code is not complete yet ! I've been adding some features! '

-'Is it possible that you migrate to another demo sub domain? Content production team wants to upload more content on that sub domain '

-'Sure ! Why not :('

we had a front-end dev that needs to "re-architecure" his codes when we need to add a small change or a feature.
and im like: wtf is wrong with your code and you need to re-architect it every damn time?!

PS: that dev is no longer with us now. thank god.

So I got this new job as Java developer, the people are really great but is the kind of companies that only takes care for fast results and not for code quality.

Because this I have to deal with libraries updated 4 years ago, classes with 8000 lines, methods with 500 lines, a WHOLE lot of work arounds because there is no time to really fix the issue unless it affects directly the customer (something not working or being really slow) aaand we use fucking svn.

Some of this practice's they know and encourage it (+1000 lines classes for example) and every time I try to talk about good practices in the code everyone seems so interested but there is always no time.

Sooo I will stay here for at least two years, I hope I can make a change for good in their code smells.

I'm going to be that guy .... A lot of these rants are about code compiling first time .. Throwing away code you wrote because you didn't need it... Getting in the zone and writing a billion lines before you compile .... Am I the only freaking person here that does TDD ? My rant is wake up people ! People evangelize about it because it fucking works !

I was wondering why every time my my code is accessing the !valid() part to later realize I was coming back to it = its state is reset = I need a break T_T

P.S. if you find anything in my code make sure to let me know :)

I really feel like coding right now, but I don't have time. Problem is: when I do have time and I have to code I probably don't want to anymore.

EsLint => 3n errors in you code.
Program failed to run

Removed ESLint

And application ran forever

EsLint is like that mother that warns her daughter time to time. Dont sit like this. Dont play with your hair. Dont whistle

Something isn't working, I play around with the code, and try all possible things in the code. Still it doesn't work. Spend a couple of hours reading each and every line but still in vain. Finally, I find out that I was editing the wrong file (same file at another location) the whole time!! This happened a couple of times when I was a newbie, one of my most annoying mistakes.
Lesson learnt: Now when anybody asks me to debug his code, I first edit/add a print statement to make sure this is the correct file. I thought I was being skeptical, but it has saved me a lot of time (mostly interns do this rookie mistake).

When you see

int i = 0;
while (int i == 0) {
//Code where nothing changes i
}

If you're going to create an infinite loop you could at least write it as

while (true) { }

and save me a little time wondering what the hell 'int i' is for!

Found this beautiful piece of code, that I wrote apparently a year ago .... oh my 😂 🤦‍♂ 😅
If I could travel back in time, I would would slap myself for doing this. Although I remember, why I did this, because of many min()/max() operations that I needed. I wanted to keep the code, so that I would know, which code piece belonged to which part, but man ... is that badly written! Nowadays with Clean Code style, I would certainly do it differently.

Modern cross platform mobile app development is a lie. Maybe if you do Apple first, I don't know. Maybe xamarin is better than Cordova, idk. I've spent more time tweaking to one platform than I would have just starting with a platform and writing two or three code bases. I've got more if iOS statements than I know what to do with and the Windows code is some hacky transpiled mess because UWP isn't ES6 ready for reasons. Also, some error and image handling just doesn't translate. All this and I've got significantly less features than I could have implemented in the same time writing in a native language.

Serious question: If a highly intelligent being, better than humans, is about to code something, how would they probably do it?

Will they use the same concepts like control flow, iterations, types, operators, object inheritance, etc?

If they are quantum capable, how can they code with booleans when it can be both true and false at the same time? Will they code truthy and falsy with another dimension like time-space temporality?

Do their code simultaneously modify the hardware or bio-hardware as it iterates over the outcome of the code?

Does input and output even relevant to them?

How do they represent infinites?

Do they have similar github workflows or they telepathically update the source code?

Do they embed their program in their DNA? Then pass to offspring the codes they already created?

Do they code using a language or do they use some frequencies and material science that simultaneously show real world output?

And do they have their version of devRant?

So I'm approaching a 8 year anniversary working in IT and this feels like the first time needing to do a serious rant.

Today I've come across some code (infact just a single line) written by another company that is so fucking fundamentally stupid that they should be banned from writing any code ever. Like holy fuck.

This is textbook examples of shit never to do ever in any fucking environment or intranet/extranet etc. What the fuck. The fucking muppetry involved in this. This is what they teach novice programmers - you see this code written 20 years ago? Never fucking do this. You see this company that went bust 10 years ago? It was because of shit like this. Never ever write code like this or your 90kg ass will be thrown 300m by the greatest medieval fucking siege engine ever created after we throw you through the catastrophic gaping hole in time and space that your line of code just created.

Fucking fuckity bye.

when you get to Friday and realized you've had almost no time to code this entire week. There is always next week.

Is it just me or do any of you people also hate asking for help with understanding other devs code?

At the same time I also hate explaining my code to other devs, like I have to justify I'm not an imbecile.

Posted a question on Stack Overflow today for the first time in as long time... Have lost faith, what shit some suggestions people have.

- Clear the cache, check again...🤨
- Your code is wrong, I tested it my way, you need to change.😒

Read the fucking post properly and gauge some level of expertise... I clearly wrote that it WAS working, the bull shit your detailing is completely irrelevant.

Fucking idiots...

What is worse than React native? A crash in flutter ....

They need to work on their stack trace all it's errors lead to framework assertion failed, but which fucker in my code caused it....

No one knows, time to play cat and mouse with this thing 😒

At work this 4X Founder ex-FAANG fractional CTO TEDx {insert_puffery} was brought in to say "It's not about code, it's about solving problems." What he's really saying is it's time for me to rip a fart in the middle of his webinar footage.

Just had to debug a piece of code for the 5th time today and I'm starting to lose my mind. Why do programmers insist on using single-letter variable names?! Is it really that hard to come up with something more descriptive? I mean, I get it, "x" is easy to type, but so is "counter" or "iterations". Does anyone else feel like they're just constantly fighting a losing battle against the entropy of poorly written code?

You all know that these AI dev tools are reading your code right?

It is sending it back to a data center and doing evaluations on the code. This is like handing your code to an unknown entity with no guarantees for privacy or copyright protection.

This concept bothers me and I would have to consult with my employer to even determine if we wanted to take that risk. I think it is just a matter of time before a bad actor takes advantage of this and rips off a company somewhere.

WRITING CODE ON PAPER...smh

I know many people wrote about this already, but writing code on paper is one of the worst things of a CS class. I’d rather get a computer with no internet access and use a notes app to write code instead of having to write everything by hand. It takes so much more time that you could spend thinking about the problem. Not only that but also my hand gets tired of writing...ughhhh

I need to convince my teacher and the school to switch to writing code on computers! I will not loose this battle ahah

I remembered one time my freakin prof in programming taugh us how to understand computer language, that time my worst enemy is ASSEMBLY, for some reasons my teacher doesn't know how to code in assembly like wtf?

On our last grading period he asked us to create a program using mov and shift and the deadline is set tomorrow after he announced it.

I remember my code in that freaking subject

MOV COURSE
SHIFT SCHOOL

HAHAHAHA after that I was scolded big time 😂

What is your first memory of programming?

I remember quite vividly writing C# in a notebook at church to pass the time. I did actually use some of that code if I am remembering correctly.

Being 26 learning to code with intention to do it for a living is hard, I wish I never gave up the first time I attempted to learn a programming language when I was 16 I'd probably be making a shit ton of money...

The time you take to code something is the time people take to quit vim. P.S. the meme below is not mine.

probably every time I see my tests failing.

Each time I am writing tests I'm convincing myself "it's an investment", "spend 2 hours now to save 2 days later", "unit-tests are good".

And each time I'm chasing away ideas like "perhaps they are right, perhaps writing unit tests is a waste of time..", "this code is simple, it should ever break - why test it??", "In the 2 hours I'll spend writing those UT I could build another feature"

Yes, it is terribly annoying to write tests, especially after writing the production code (code-first approach). Why test code that you know works, right?

But after a few weeks, months or years, when the time comes to change your feature: enhance it, refactor it, build an integration with/from it, etc, I feel like a child who found a forgotten favourite candy in his pocket when I see my tests failing.

It means I did a very good job writing them
It means it was not a waste of time
it means these tests will now save me hours or days of trial-and-error change→compile→deploy→test cycles.

So yeah, whenever I see my tests fail, I feel warm and fussy inside :)

If you're stuck with something and just cannot figure out where the issue is in your code, there is nothing that helps you more than talking the problem out with someone.

Most of the time you'll end up figuring out the solution yourself while describing the problem to him/her. =)

> do you feel sorry for freelancing contractors
> whose previous client abandoned them
> they ask you to help them fix some trivial bugs in the shitty code
> you believe you can change the world by going overboard by also improving the code quality, along with fixing the bugs
> initialize an empty file where you'll translate the shitty code into a more organized one
> start creating variables and generic functions which can be used in a modular and organized fashion
> meticulously document the first function you write
> realize this is not worth your time
> insert some glue code into the original code which fixes the trivial bugs
> glue code has hard coded values so it adds to the shittiness of the code
> submit the work
> get $$$

I get listening to music while you code, but I’m afraid I just can’t believe in watching a TV show while you code. You’re not coding, you’re watching a show. Or if you are coding, the level of code that’s being written is probably low enough to make it a waste of time.

Devs with young kids: how the hell do you do it?

I am a foster parent for my cousin who is 4 months old and I don’t know how in the fuck to make this work. How do you do it? How do you balance code and kid?

For reference I work full time at a tech support place, I go to school full time, and I’m trying to pivot into software development, which means any free time is spent coding/studying code/building a portfolio. Problem is I don’t have free time because of the baby. How in the hell do people do this.

THE TYPESCRIPT DEFINITIONS SAGA CONTINUES

> IHateForALiving: so, I don't really know which field we're supposed to use here, but that's your entity I'm working on, so...
> TeamLeader2: wait, what is this? Why does your code have autocomplete?
> IHateForALiving: Every time I worked on some parts of the code I've been writing some type definitions along the way, and it's adding autocomplete if you type hint your code... but I've been told not to write them anymore, so I stopped
> TeamLeader2: But why tho? It's so fucking handy
> IHateForALiving:

Hmm. Seniors have the half working experience as I do and I am the only not senior one in Dev team.

I adapt code only to "taste" good for code reviewers, but they allow themselves to commit without caring and just saying :"oh unit testing is boring"

Enough with the kindergarten. Time to prepare myself for the next job.

Hardest thing for me as Team leader is to teach people in my team, that task is done, when unit tests are written, pull request is created, approved and merged.

Not when their code compiles for a first time.

Every morning I start visual studio code from cmd... So I wanted to make a script to open that specific folder and start it in code...

The time I spent trying to make this thing is longer than the time it would take me to start code every morning.

Guess I'm no hackerman :/

confession time:
I am php laravel developer with little knowledge about nodejs.
I got selected by one startup as nodejs developer.
frankly I am not better nodejs developer than my competition who were rejected.

I completed oral interview with my nodejs theory knowledge at a time of technical round , they gave us task to create crud with fantastic front end and nodejs mongo as a back end.

I developed front end in bootstrap but at a time of backend, I just copy paste code from github.

and changed everything variable and other proof to hide reality. in mean time other candidates were actually coding everything then I took time to understand this code and I submitted after few candidates.

in last round they ask me to explain code which I explained properly and I get salary 40k/month INR.

I know it is cheating but I wanted this job badly.

I just hate wordpress. Whenever I have to touch it, makes me nervous.

This time I just have to put some html/css. I was thinking it's piece of cake.
Couldn't be more wrong. This fucker is adding extra tags to my code fucking up what made...

I think one of the most amazing things about being a developer is seeing the abstractions that have come about over time. From having to program in machine code and assembly, to now with languages like Java, where a lot of the boilerplate code is effectively abstracted out by frameworks.

Your "feature" just became my problem. Your "great idea" is now my migraine. What you did in 300 lines, another team was already doing in 5.

The next time you `brew install...` on your laptop, you should fucking think that the infra team has to install those dependencies, on every server, too.

In less time than it took you to create your code, I could have given you several functions to call. I could have saved all of us weeks of work. Fucking ask cross-team before you cowboy code your next big idea please.

Got a problem you need to be solved, somebody else probably solved it, just fucking ask.

Why printer services is stuck in time?

The windows printer spooler is old like my grandma. He fuck all the time but nobody wants to recode it ? I need to search for old driver a day long to make it fucking work at 10%

On linux generic printer driver do the job but cannot do all the things you want

Why is so fucking complicated all the time ? ( Don't think that scanner work you don't have de correct driver )

Solutions printer share the code for how de fuck i work ?

Re-reading old code I wrote some time ago and trying to improve it. It sounds and it definitely is scary to do at first, but it truly helps me approach things from a different perspective and question what I did.

You will get far more rejections than acceptance. A lot of the time it has more to do with the interviewer and not the candidate (assuming the candidate is a genuine hard worker). The job search process is similar in this regard to finding a mate or compiling your code.

Keep moving forward!

Guess you guys don't care about goals like "losing weight" and that stuff. So my code-related goal is MASTER VUE.JS ONCE AND FOR ALL. Seriously, I need to start using it in production or I will keep wasting my time.

Asked to do overtime so I do. Everyone has gone home and now it's time for me to go home, so I go to leave the office to find the gate padlocked. I'm stuck. There is a side gate for cars that has a security code but I have no idea what that code is. So I end up waiting around and stalk the cleaners car out of the gate 'sigh'.

I havent touched swing in months, and now when i need to come back to it everything is Windowbuilder. Trouble is, nothing is included in Eclipse and I don't have time to go around hunting for the packages I need. Netbeans is marginally better, but GODDAMN its frustrating when it auto-gens code that you have to use N++ to edit...

The ratio of time spent reading versus writing is well over 10 to 1. We are constantly reading old code as part of the effort to write new code

- Robert C. Martin

IBM: "oh, you can't actually USE our watsonx garbage, you need to book a call first! yes thats right, waste your time before installing what is nothing more than a chatgpt plugin for VS code!"

yawn

simply iq destroying knowing companies operate like this

🤡

Title: The problem with "good enough" code

Body:

I'm a software developer, and I've seen my fair share of "good enough" code. You know the kind of code I'm talking about: it works, but it's not pretty, and it's not very maintainable.

The problem with "good enough" code is that it's a slippery slope. Once you start writing "good enough" code, it's easy to fall into the trap of always taking the easy way out.

Before you know it, your code is a mess of hacks and workarounds. It's hard to understand, it's hard to maintain, and it's a nightmare to debug.

I've seen projects go down in flames because of "good enough" code. The code was so bad that it was impossible to fix, and the project had to be scrapped.

I'm not saying that you should never write "good enough" code. Sometimes, you just need to get something working, and you don't have the time or resources to do it perfectly.

But if you're going to write "good enough" code, you need to be aware of the risks. And you need to make sure that you're only writing "good enough" code for a short period of time.

Once you have a working prototype, you need to start refactoring your code and making it better. You need to make it more readable, more maintainable, and more testable.

If you don't, you'll eventually regret it. Your code will become a liability, and it will hold you back.

So next time you're tempted to write "good enough" code, think twice. It might save you some time in the short term, but it will cost you in the long run.

At what moment do you realize you need to stop coding? Mine is when the code starts bleeding together. Like when I start putting config file information into my methods, which I ended up doing tonight. 😖 God it's time for pizza. 🍕

So I work full time at a retail store, but only one person is on shift at a time here so I'm allowed to bring my laptop and code while I'm running the store. This is where I get most of my schoolwork done and make most of my project deadlines for web dev job.

My only social life really consists of me hanging out with my boyfriend. Often when I need to be working on some code or project he will sit next to me and play guitar/sing or will quietly read while I'm on my laptop.

Other than that I chat with some game friends through Discord throughout the day, and often visit/help family members in spare time off of work.

Not much of a social life when you're super busy

This just happened. I have to tell someone how stupid I felt a few minutes ago.
I am working on a script that is supposed to rename some files in sub folders of the current folder.
I used ChatGPT to help me out with the last part of finding all sub folders. Copied the code into VS code. Changed the path from “/path/to/folder/“ to just “/“, ran the code. It took a bit too long time to finish. Then VS Code asked for permissions to my reminders… “Why?” I asked before I realized that I confused “.” With “/“ for current folder…

I always try to break my code when it works without errors the first time.

Just to be sure that the code I wrote is being used.

Anyone else?

Security : Each time I login, they ask me to type the email address I want my one-time-code emailed to. Really!? What security is provided by letting the user decide where to email the flippin token to?!?!

My Gripe With Implicit Returns

In my experience I've found that wherever possible code should be WYSIWYG in terms of the effects per statement. Intent and the effects thereof should always be explicit per statement, not implicit, otherwise effects not intended will eventually slip in, and be missed.
It's hard to catch, and fix the effects of a statement intent where the statement in question is *implicit* because the effect is a *byproduct* of another statement.

Worse still, this sort of design encourages 'pyramid coding recursion hell', where some users will first decompose their program into respective scopes, and then return and compose them..atomically as possible, meaning execution flow becomes distorted, run time state becomes dependent not on obvious plain-at-sight code, but on the run time state itself. This I've found is a symptom of people who have spent too much time with LISP or other eye-stabbingly fucky abominations. Finally implicit returns encourage a form of thinking where programmers attempt to write code that 'just works' without thinking about how it *looks* or reads. The problem with opaque-programming is that while it may or may not be effortless, much more time is spent in reading, debugging, understanding, and maintaining code than is spent writing it--which is obviously problematic if we have a bunch of invisible returns everywhere, which requires new developers reading it to stop each and every time to decide whether to mentally 'insert' a return statement.

This really isn't a rant, as much as an old bitter gripe from the guy that got stuck with the job of debugging. And admittedly I've admired lisp from afar, but I didn't want to catch the "everything is functional, DOWN WITH THE STATE" fever, I'm no radical.

Just god damn, think of the future programmer who may have to read your code eventually.

How greedy can you get?

> boss takes half assed gdpr project : branch xyz
> branch xyz requires deprecated version of npm/node
> I re-install node this time with deprecated version
> Wow this node is configured with ant build
> ECMA 5, config but code is shit as fuck
> still I get the job done , cannot test it because code is shit as fuck and I will never any thing to fix that un healthy code
> code doesn't run on client side,
> no shit Sherlock
> get a call from boss, it urget look in it and fix it

Agencies... Just hate when people are given only time enough for doig crap code, because "there is no budget". Hate even more to work on changes on top of it, because people just dont get why you take so long to do changes that supposed to be simple, ignoring the fact that previously they asked for some slap-dash shit. What do they think, that with time the code cleanup and tidy up itself?

I am pretty sure that I am not the only one who is lazy as Fuck most of the time but when I sit to code I write enough snippets that can be combined to form Baxter building.

Why is sleep not a choice. I have code to write but my body and mind wont let me stay up.

Too many projects so little time

No one to help 🙃

Sleep is really a devs enemy 🙆🏾‍♂️

I don't care about your good ideas.
If you don't code, don't art, have nothing to contribute to the work, and aren't going to pay me for my time, then there is no collaboration.

So. It is that time again. The last week of the semester for college students. Paper due for all, presentations for everyone and their moms and final in a week for which no one had the time to study and I'm here wishing death so I can code in piece in the afterlife.

I just used Visual studio c++ for the first time. In comparison to intellij it just sucks, so many features are missing, im fighting with the editor all the time.. For example Code completion, visual studio suggests me the method name, i press enter, new line inserted, wtf? Apparently only tab is working here, next try, visual studio suggests method, I click tab, method name inserted but whithout brackets, omg. The standard shortcut for commenting out code is CTRL+K followed by CTRL+C, if you want to use the code again you need to use CTRL+K followed by CTRL+U. HOW STUPID IS THIS? Refactoring of code, e.g. Method names also sucks...

Anyone who formats their code manually is a fuck there I said it.

Also stop using a tool that has no contextual understanding of your code. You're wasting more so much fucking time trying to guess shit that an ide would automatically know and doing stuff that an ide would automatically do.

Man all I ever do is fix bugs in a giant overgrown calculator, that has references to code before I was even born. It might be new job time

Famous quote time! I forget who said it, and the number varies a bit from one retelling to the next, but one that has always stuck in my mind since I heard it is the following:

“I’d fire any programmer who spends more than [10 | 25]% of his time coding.”

I’ve always taken this as an admonition to spend time charting out solutions before building, instead of churning out stream of consciousness spaghetti code, personally.

Any thoughts from the broader community on the topic?

Just found out my company's API for the payment took 15 seconds to respond. WTF? Personally I have done countless of these kinds of API , but this is my fifth time witnessing bad code.

By always striving to do better each time. Making code less sloppy every time I write GL code. Better performance everytime I write an algorithm. Lower memory usage every time I write application state. Learning a new trick for an old problem, one at a time.

Learning best practice in one go is impossible, but taking it a bit at a time makes things more reasonable.

I was away for a long time. Now I got a new job which means it's time to start ranting. Fuck this legacy code is worse. I mean, a fucking cat running after a mouse could write a better source code if he had somehow pushed buttons while doing its job. Every fucking best practice I know is crushed to bits. And the funny part is, this company/startup recently got $300.000 funding.

I've found a new genre that is really nice to listen to when I'm doing homework or the rare time I code some.

Bluegrass banjo music. It's pretty simple and it's never slow. It's off but if it works, it works 🤷🏻‍♂️🤷🏻‍♂️

>Be me, humble physicist turned quantitative developer
>Big physics nerd, but code for the cash
>Working on some quantitative finance software, all about risk measures
>Girl comes over one day, cute as a quark
>Think to myself, "This is it, time to make a move"
>Instead, brain decides it's time to explain my work
>Start rambling about refactoring, polymorphism, and data encapsulation
>She's looking at me like I've started speaking in binary
>She tries to steer the conversation back to normal stuff, but I'm stuck in a recursion loop
>Keep going on about my project, can't seem to stop myself
>She tries to stay longer, even tries to show interest in my work
>But the more I talk about algorithms and time complexity, the more her eyes glaze over
>Eventually, she gives up, says she has to leave
>She leaves, probably thinks I'm more interested in my code than her
>mfw I realize I've chosen code over companionship
>Why am I like this?

So it turns out that a lot of writes to S3 is slow, regardless of whether you spent the time to rewrite your code from SAX to JAXB, then Go, then finally C++, thinking the problem was always with your code.

Long days back it was time taking to hack wifi password using coding on Linux kali ,by using few lines of codes etc,,

Nowadays Linux's kali's fern wifi cracker is too easy to use instead of using lines of code.
LOVE TO USE LINUX KALI

So there is this program with legacy code from 15 years ago the client is in love with. Every time we try to accomplish something it proves that the mf who wrote it was so lazy and incompetent that he should have never chosen this profession. Goto, one-two letter for type and variable names. Dude even wrote an ascii decoder as if he would be payed for lines of code. Today we found a code where a rows of data was misindexed by one (we incorrectly assumed that we could extract some data from it but the column we wanted to use was just there for decoration, it was not actually used). the calculations the system uses are replicated for each interface with duplicate lines of code so the same binary data can show different values because of the multipliers.

If I could I woukd go back in time and bang the guy's head to the desk emphasising each word like "You - should - quit - and - never - ever - write - code -again"

I'm so fucking done with this shit. If someone forgets every git command every single fucking tim le is ok to ask. Every time someone asks advice on how to write a fucking retarded workaround (out of lazyness, because fixing their own code is too much to ask), it'a ok.
The *ONE* fucking time i ask the name of the fucking function to generate a filter via code using their fucking cms? "you should do that via gui!" "who cares if there'll be conficts with git, just manually redo everything in production!".
God fucking dammit how can you even have the balls to complain about terrible planning and stuff not working if that's your fucking mantra?!

My C# teacher. From all the beginning CS classes that I have taken she is the only that I really respect. She took the time to teach us how operators work, took the time to teach us Pseudo code, and made us code using just a pen and paper. I bought my laptop (instead of a desktop) to code along her in classes. She would ask us how to solve something. Gave us like 5 min to think about it, and then we would answer it, and she would translate our solution to code making comments for us to fully understand what was going on.

You know that time when somebody had a problem with a system you wrote years ago, and it has taken you an hour to try to remember how to even call it, because the documentation and code didn't get migrated from svn to git, and the svn server has been shut down for some reason, and the admin is out today, and the last time you had the code was three machines ago, so you're trying to gleam what needs to be done to just call the stupid thing from log files set to 'error'?

That time is now.

I think one of my biggest mistakes as a dev in the becoming is to have tried to produce code rather than think code.

The patience to try and understand a problem rather than just solve it.

After spending 2 hours on what seemed like a ridiculously small issue，i know what the problem was before solving it.

Which meant i did take longer to solve it but i DID NOT take the wrong direction. Which would ultimately have come back to my face some time soon.

Coding takes a fuck load of time -_-.

I probably dont balance it well. I spend majority of my day either reading code, reading about code, or writing it. I would say my balance comes on the weekends. I hang out with my girl more and I not in front of the computer as much. But even on the weekends I sneak in a few hours of code. My leisure time is literally sitting at a starbucks with my favorite text editor listening to a playlist and coding. That's like total zen for me.

Tbh this is more about education in general... Introduce the same system i had, no fixed lessons just a project and a time frame. Eg : create your own MVC framework and a site to show it off

Time frame : 5 weeks

(dont expect fully fletched frameworks but a site that uses the MVC data flow and the code is reusable)

I'm in highschool learning to code, but I already realize that a programmers biggest enemy is TIME! I don't have time do the projects and learn the stuff I want to fucking learn! Because of God Damm School!!

It's the first time since I finished high school (2 years ago) that I get to review my CV. I included as one of my features that I liked to write "optimized code" and just realized how wrong that is. Those where the times when I had little to no experience at all and would spend unreasonable amount of time to write programs with the fewest lines possible (I loved python because its one-line capability).

I think it's time to rewrite that CV.

Reading code takes time!

Everytime I read:
"var" or "auto" Add: 10s
- Just use the type

Everytime I read:
if(Expression1 && Expression() ? GetNumber() : 0 > 0) Add: 30s
- Just write two if statements or create two bools the line above.

Everytime I read:
delegate = () => {} Add another 5 minutes of reading time.
- Just write a separate function for it. It helps with searching and understand what it does

Please code like the person that needs to check your code or change it just knows basic coding skills and logics.

I do know all these concepts I just never use them because it makes the code unreadable. hard to follow, mistakes that can happen everywhere. difficult to search.

And it frustrates that I need to read 10 extra lines to understand code flow or hover my mouse in an IDE to figure out what type object it is.

It's properly just me... I just like clean readable code. that is logical and failsafe and strict and deterministic with its behavior

"Some time ago I wanted to rewrite my old project. I saw code without comments and cried. Cried so much."

Programming teacher in college

People who teach us programming usually write a quicksort every year for 5-10 years. It is sad af :(

Web code editors are shit for interviews!!

I was given a timed interview test to code on a hackerearth’s code editor. First of all I have never used hackerearth’s code editor because they suck. The problem was very simple and I cleared the round anyways when an actual human saw my code. But my point is why are programmers creating shit editors for other programmers in a timed environment. I couldn’t figure out for the life of me how the fuck I should take an input and output that in this shit editor. The code logic was ready but the test cases failed.

So Should I be learning about hackerearth’s shit code editor in an interview with a timer or should I be judged on the code logic in the specified time?

I seriously find these web code editors most of them annoying. Cause they aint good enough. You need time figuring out the tools first and then code the logic.

Usually in your job you’re gonna use the editor of your choice. Not a fucking shit fucked half arsed hackerearth code editor. My rant is for those of you if you’re taking interviews on such platforms, be there. Don’t rely on those platforms. This automated crap is still crap.