Anybody tried code licking to solve your problems?

How it should be:
- First: solve the problem
- Second: Write your code.

How many people do:
- First: Write code
- Second: solve code problems
- Third: Adapt code with requirements
- Forth: get lost on your spaghetti code
- Sixth: make a suicide

Reading devRant feed is so fucking hard nowadays. Every other rant is about Windows rebooting, Google being evil, Quantum beating Chrome, M$ users being cunts and all these fanboy shits.

Fucking hell. Write some actual code and rant about some solid problems rather than being a stupid fanboy.

One of my worst meetings, as the sheer rage was unbelievable.

Backstory:
Architect: "Stop duplicating code", "stop copy pasting code", "We need to reuse code more", "We need to look at a new pattern for unit tests" etc.

Meeting:
Architect: What did you want to talk about?

Me: I built a really simple lightweight library to solve a lot of our problems. Its built to make unit testing our code much easier, devs only need to change a small bit of how they work.

Architect: I like the pattern a lot, looks great ... but why a library? can we not just copy the code from project to project?

... do you have a twin or something?

Bad architecture causes more problems than bad code.

You are the CSS to my HTML,
You make my life so beautiful.

You are the JavaScript to my code,
You make my life to be so dynamic and full of life.

You are the OS in my life,
Without you, am useless

You are the C: to my brain,
Without you am nothing.

You are the stack overflow to my problems,
I run to you for solutions.

To be continued.....

10-1 AM - 4 of us got drunk.
2-4 AM - 2 hours straight coding, solving big-ass problems
10 AM - Fucking hangover and python code in a java project!

Me and my senior used to do doodle in papers whenever we get stuck in some code problems or having free time. It always has been our way to relax our mind kind of meditation.

One day our boss saw our doodle work. He asked us to do doodle in office wall. So far this has been our progress.

Jobless.
Nah, just kidding.

I'm a qualified teacher, so I have that to fall back on.

That or fixing things, I suppose. I would then design something to corrupt that AI and then I can get hired back when the AI starts its reign of terror.

"Oh no! The AI became sentient and started intentionally fucking code up (and then proceeding to manically laugh at it ((ha...ha...ha...)! Who can save us?"

"I have a team of highly skilled devs, programmers, and a dude who works in a cellphone shop at my disposal. devRanters assemble! (then I just fuck up the code I made initially to make them sentient and commit it - problems solved.)

I used to work in a role that was basically tech support for engineers. Folks would call, we'd look at their code and see where things were going wrong.
One customer calls in, they're having timing problems with a satellite control system.
I dig down through their code, and buried in one of the modules is a comment to the effect of:
"Once we upgrade to Windows 98, we'll need to change this call to the precision counter"

They never did.

This system was running XP.
Somehow, they'd avoided destroying satellites despite having the code run on Win98, and ME without fixing that call. It wasn't until they upgraded to a multi core system and XP that their gyros stopped responding correctly.

Holy shit.

Best part of being a dev? Being paid to fix problems in the code you created yourself.

Stackoverflow

When I was just starting with programming I used to google a lot (more) of my problems. But just just copying them made me feel guilty, since I could not handle the problem myself. So I decided to analyse a code to the point where i understand exactly how it works. Sometimes it took me a couple of hours to understand a method, which was written 1 or 2 levels over my current level, but it was totally worth it. I learned a lot about Java, how to write cleaner code in general and how to read and understand code quickly.

(c) Creative Tim. Worth to read pips!

How to land a programming job

1. ABC (Always Be Coding) - The more you code, the better you'll get.

2. Master at least one multi-paradigm language - Some good candidates are C#, C++, Java, PHP, Python, and Ruby.

3. Re-invent the wheel - You should implement the most common data structures in your language choice.

4. Solve word problems - Pick those that test your ability to implement recursive, pattern-matching, greedy, dynamic programming, and graph problems

5. Make coding easy - At least, make it look easy.

6. Be passionate - If you don't care, then nobody else will.

7. Don't make assumptions - Ask questions if you're not sure.

Attack problems you've never solved.

Don't fear projects which you're not familiar with the technology.

Read books, blogs, and code.

Refactor every opportunity you have.

Don't always be the smartest developer in the room.

Be flexible. Tools are tools, don't fall in love with any one till and neglect others.

Cant find the off switch

#2 Worst thing I've seen a co-worker do?

Back before we utilized stored procedures (and had an official/credentialed DBA), we used embedded/in-line SQL to fetch data from the database.

var sql = @"Select
FieldsToSelect
From
dbo.Whatever
Where
Id = @ID"

In attempts to fix database performance issues, a developer, T, started putting all the SQL on one line of code (some sql was formatted on 10+ lines to make it readable and easily copy+paste-able with SSMS)
var sql = "Select ... From...Where...etc";

His justification was putting all the SQL on one line make the code run faster.
T: "Fewer lines of code runs faster, everyone knows that."

Mgmt bought it.

This process took him a few months to complete.

When none of the effort proved to increase performance, T blamed the in-house developed ORM we were using (I wrote it, it was a simple wrapper around ADO.Net with extension methods for creating/setting parameters)

T: "Adding extra layers causes performance problems, everyone knows that."

Mgmt bought it again.

Removing the ORM, again took several months to complete.

By this time, we hired a real DBA and his focus was removing all the in-line SQL to use stored procedures, creating optimization plans, etc (stuff a real DBA does).

In the planning meetings (I was not apart of), T was selected to lead because of his coding optimization skills.
DBA: "I've been reviewing the execution plans, are all the SQL code on one line? What a mess. That has to be worst thing I ever saw."
T: "Yes, the previous developer, PaperTrail, is incompetent. If the code was written correctly the first time using stored procedures, or even formatted so people could read it, we wouldn't have all these performance problems."

DBA didn't know me (yet) and I didn't know about T's shenanigans (aka = lies) until nearly all the database perf issues were resolved and T received a recognition award for all his hard work (which also equaled a nice raise).

I hate all of these rants about JavaScript being a terrible language.

In reality, it's one of the easiest languages to work with. This makes it easier for new programmers to write messy code, but is it the language's fault?

People get mad about the things that happen when you multiply "undefined" and a string...what do you expect?

You also have the freedom to choose from a variety of tools the community has created to solve existing problems. People just don't realize that they don't *have* to learn everything, you just learn as you need them.

Don't blame JavaScript for you bad programming, terrible type conversion needs, and great tooling.

My anxiety is kicking in again.

I want to build something meaningful outside of work but my mind is blank, I have no ideas to implement, and whenever one pops up in my head, I DDG it, I find that there's someone who already built something similar and I lose all interest.
I want to code, but I'm tired of solving fictional problems.
I miss being excited to learn a new tech, since I know I would ditch it if I can't find anything to build with it.

This is causing me to lose all motivation to code and learn, I really hope this is just a phase ｡ﾟ･（>﹏<）･ﾟ｡

My biggest hurdle is learning to code all by myself. I never knew anyone that I could ask for help or discuss problems with, because there weren't any programmers in my family, and my friends were too busy playing video games.

I have no words to describe how I'm feeling these days. I have to do a C project for uni.

After a couple of years dealing with web dev, javascript, typescript, angular and stuff, for the first time I have a project where I have to deal with only two problems:

1) my code
2) my machine

No tools, no bloated libraries, no webpack, no json configurations, no tutorials.

It's just me, vim, gcc (actually nvcc, it's a cuda based project, but still) and the cuda manual.

I feel I'm actually building something.

Plus, the guy I'm doing the project with is cool with this stuff and most important he's open minded.

I'm happy

Functional Programming. Because Moores Law has moved from making processors faster to multiplying cores, and we may eventually have to code on machines that have 1024 cores or more. Mutable state will cause all kinds of hell in those scenarios. We already have problems with it when we have like 2-3 different threads.

ME: I'm having problems with my parents
GF: Why don't you talk to them?
ME: I can't
GF: Why not?
ME: They're made of code
GF: ... thinking... ~face palm~

Adventures in security land, part II:

I’m getting pulled off the security review team and instead relegated to part-time security tickets alongside my usual dev work. (So, someone else finds them, i fix them.)

Guess I found and debated too many problems with the lead dev’s code. 🙄

I need to take a break..
I've been wotking on my game non-stop for the past 8 days from 7-10am to 11pm-2am..

But there are alot of problems in my current repo, and i have ALOT of code to re-rwite..

(also i'm the only dev x.x)

When my boss asked me to write tests. Here is what I said... :P

New semester, new problems....

Just started my 6th semester at uni and my teammates are already proving to be serious dumbfucks..

They want to keep all files neat and organized, sure, fine, good idea.
They want to use Dropbox to store code and our LaTeX report, no, never! Somehow managed to get them to switch to GitHub, yay!
They want to have everything in one fucking repo! Why? Oh god, why? And I can't change their mind on this!
And they still want to use Dropbox to have a backup and sync between their machines...

So during this semester, we will store our LaTeX report and the, at minimum, 3 code projects, in the same repo organized by folder!
Why not one project, one repo? Then I won't have to pull all the shit code that I don't have to work with!

Expect more rants in the coming months...

The best part about solving problems in code is there is no one right answer.

Except for this. This is clearly the wrong way. This is garbage and you are a garbage person for writing it. This code you wrote is the reason your own children will never love you.

if (questionAsked) {
retuen "It depends...";
}

I hate it I hate it I hate it

But it's true because there are a fuckton of factors that determine the answer to a question and nobody ever knows all of them.

I can rarely answer a question from classmates or non-techs without saying that it depends or that there are multiple options.

"Are statics ever good?" It depends
"Should I inject this dependency?" It depends
"Should I google every question first?" It depends

I fear giving a whole answer without knowing the details or at least seeing the code. I've come across multiple XY problems and I'm glad I took the time to look at some code first.

Fuck College, Fuck C, Fuck the people that didnt help me with my C code and in fact made my problems worse and didn't fucking help me, Fuck the bastard that decided to give my the largest mountain of homework, fuck my inability to get shit done, fuck myself for not getting motivated to do anything. And also fuck Javascript cause its JavaScript.

Edit: IM ALSO FUCKING RETARDED

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."

When I discovered Clean Code, design patterns, TDD and BDD. It just clicked. Ever since everything build so easy and obviously. I no longer have most of the code problems folks rant here about.

That's when it came to me: it's not enough to know how to write code. To climb off those amateur shoes I must adopt those methodologies, so that the code would be decoupled from me, from my style, and I've got to let tests drive my code rather than vice versa to have a flexible and reliable codebase that is cheap and easy to maintain/extend.

Me (as a Senior developer): How will you solve this problem using regular expression?

Junior developer: *Explains*

Me: Good

Junior developer: I truly feel like a programmer when I code regular expressions

Me: Now, we have two problems.

Once a day, take some time to read your colleagues' commits.

You will see how they work, you will learn how they solve problems, you will understand their flow and you will know more and more parts of the code base.

So I met this Professor in my campus recently.. This life-changing conversation followed :
Prof: What are you doing on your laptop?
Me: Sir, I am practicing some coding problems.
Prof : Coding problems? What's your branch?
Me: Electrical Engineering.
Prof: You aren't expected to code. And you aren't taught much coding in your coursework too.
Me : Sir, I take it as a passion and I did learn coding all by myself.
Prof : Rubbish. Learning coding by yourself is similar to saying that you don't require a Prof. to teach you. Just focus on your subjects and stop wasting your time.
Me :Good afternoon, sir. You're right, I did waste my time here.
*Grabs laptop and leaves,hoping he won't be taking any lectures in my next sem. *

take a shower. honestly most of my code problems have been solved while showering.

One of my QA friends told me today,
" If I wanna screw you up, I will just have to delete a semicolon in your code, hahahhaahhaha ". <for real>

There are two problems here
1. He's not familiar with the concept of an IDE
2. I use Python

Stop making fucking " ; " jokes in early 2019 >_<
:P
#No hard feeling to the QAs out there

Pls send help. I having problems with following code:

Human h = WildOrangutan
.getInstance();
Ass ass = h.getAss();

Toilet toilet = new Toilet();
ass.attachTo(toilet);

while (ass.hasOutput()) {
ass.output();
h.readDevrant();
}

ass.detach(toilet);

// This throws
// OutOfToiletPaperException
ass.clean();

So, I got a recall notice for my car today. Because of brake problems? No. Because of air bag issues? No. Because spontaneously combust while hurtling down the freeway? No. Because the software developers pushed out buggy code. My car is being recalled for a software bug! I kid you not.

When you have boolean problems with your code, it's called boolshit.

How I spend my days at work working with legacy code:

* Writing tests before I do anything
* Noticing that i cannot write tests because of antipatterns. Lots of them.
* Refactoring to make at least a tiny bit testable.
* Then writing tests.
* More rewriting and refactoring
* Finally adding that one feature my boss asked me for
* Writing tests for that new feature (my do that before implementing)
* Explaining to my boss why it took me so long and agreeing on stopping writing tests.
* 2 days later: explaining why i still broke something.

But in the end my code works just fine.
my colleagues handle things differently. They just ignore problems as long as at least one feature works a bit.

I'M TIRED OF HEARING THAT DEVELOPMENT IS NOT A CREATIVE FIELD! Creativity is emerging new ideas from non-existent ones. It is not confined to pretty designs or well-written copy. Sure, devs are logical problem solvers – but not a single dev will solve those problems the same way. Code is like the paint on our dark-themed canvases and you can see yourself out if you think devs are just robotic coding machines

When the client writes a 100 page novel about his problems, but never sends the ACTUAL CODE to review.

They've literally left me with nothing to do. I'm doing nothing. I can't be happy doing nothing.

To illustrate the chaos: Everyone on the team was trying to figure out some defect. No one knows what is going on in the code. It's unlike anything I've ever seen.

I found an API call with a misspelled endpoint. It was wrong since the code was written two months before. There's no way it ever worked. Obviously no one tested the code because they would have immediately seen that the call returned a 404 every time.

I fixed it. That was my only PR in about a month. It was literally one character.

The next week that PR got reverted. Apparently the app works better if the API call fails. No one said what goes wrong if the request is made, just that it "causes problems."

That's how bad it is. No one knows why anything does or doesn't work. People write code that doesn't work, never test it, and the application works better in some unspecified way if that code never gets executed.

The last straw for me was when an architect told us that if we want to improve our skills we need to learn how to read and debug stuff like this.

1) Not to be immodest, but I'm good at figuring out bad code.
2) Just because I can doesn't mean I want to do it all day instead of actually developing software
3) He trivialized the really important skill, not making a mess like this in the first place. If his idea of skill is to sling crap without tests at the wall and then debug it, how is he an architect?

I tried really hard but I can't keep a good attitude. I don't want to become toxic, but why would I consider working that way? I try my best to be good at this. Writing decent code means a lot to me. It should mean a lot to them. Their code is costing them hundreds of thousands of dollars. Maybe millions.

I can't write good code and add value if all I do is debug bad code.

So I'm out. I'm going to another project. Have a nice life.

Last week, the team lead told me that he can't merge because my code has code smells and going forward, can't have that. We use Sonar and well the way to "fix it" according to him is to mark the line using //NOSONAR.

Most of the issues are minor like Unused imports and for me incomplete TODOs.

And before the "verbal" rule was only need to fix Major + issues. And well the reason I use TODOs is to mark code that probably needs changing in the future. I know there's going to be some feature that these lines have to be changed. But the requirements are fully defined yet from business.

But I sort of blew up on him. YOU WANT TO ENFORCE ZERO CODE SMELLS NOW?!?!?! AND THESE MINOR ISSUES? MARK THEM WITH NOSONAR?

HERE'S WHAT I THINK FOR THE LAST X YEARS... THE CODE DESIGN IS SHIT, MINOR CODE SMELLS AND MANUALLY MARKING THE ONES U NEED TO KEEP... ARE THE LEAST OF OUR PROBLEMS...

THE OTHER PROBLEMS I'VE MENTIONED BEFORE EVER. MOS YEAR BUT YOU DIMWITS NEVER LISTEN.

YOU THINK MY TODOS ARE BAD... 90% OF THE CODE AND FEATURES (THE ONES NOT DONE BY ME) LOOK AND SMELL LIKE MONKEY SHIT. UNDOCUMENTED, MESSY, FULL OF BUGS.

AND GUESS WHAT? NEW FEATURE, SOME DEV FORGETS TO CHANGE SOME COMPONENT THAT DEPENDS ON IT. WOULDN'T IT BE GREATE IF THERE WERE BOOKMARKS... O WAIT...

i just was catching up on comics again and saw this one... with triggered my memory and this rant... My first thought was to forward it to him...

To be able to code blind folded - literally. A few years back when the web speech synthesis apis came out and chat bots were raging I thought it would be cool to dictate pseudo code on the fly whole whiteboard the problem. When I investigated the easiest way to implement a mvp I was shocked to learn that there are BLIND programmers.

That alone is impressive and I went on to find that many have years of experience and add valuable contributions on a regular basis. Unfortunately I havnt had an opportunity to meet one yet but I am in utter awe of their accomplishment.

Should I get the chance I want to try and walk in their shoes, live a day without my eyes and learn to solve problems without spotting a pattern

TeamLeader: I need you to stop disagreeing with the decision of the management, the people in there are taking their decision for a reason.

IHateForALiving: When integration tests were failing, the management decided to comment out the ingration tests; god knows how many bugs slipped by.
When users had problems with the idiotic migration process the management designed, the management decided to remove down migrations; it took two weeks before the QA team started screaming, as all their machines were filled with garbage data.
I was writing type definitions for my code, you removed it. You effectively ensured the only person capable of working on that particular piece of code would be me.
I have been proposing for 8 months to make a unified scheduled jobs system, you all decided to create at least 5 different -and incompatible- implementations, at least 4 of them are total garbage with setTimeout, there's no way to ever unify them and God willing they never break, if they do there's NO WAY to find out even where tf they're hidden in the code.
Every time you were making one of those bad decision I was the only one warning you of the problems you were creating. The idiotic change of the day is going MongoDB+Angular: I can keep a low profile if you want, but when this blows up you can be damn well sure I'll handle my 2 weeks notice because there's no way on earth I'll be stuck with the aftermath of you lot taking technical decisions you are clearly unable to manage.

See, the problem with University students beginning programming is that they think that they're the hottest shit just because they know how to open cmd.exe. Since I'm a mentor, I have to give them pro tips while helping them through problems. I can't count the amount of times I've repeated "solve the problem on a notebook, write down how you should approach it before you begin typing your code, otherwise you'll end up spending more time debugging." They don't like to listen, cuz they're the next Zuckerberg. The following day I get a bunch of emails asking why their code doesn't work.

I had this one teacher that sucked some serioud dick. She refused to teach us what she was supposed to... Java.

Her teaching habits include: talking about her life problems for the whole class until the last 5 minutes to actually teach us knowledge that usually ended up being useless, refusing to answer questions and demanding that we use Google instead, and worst of all... the way she checked our programs to see if they would work. The absolute FIRST thing that she would do when she sat down at our computer, was open up our code, to see if it looked EXACTLY like her fucking code. She wouldn't even check if it worked first...

Honestly, teacher's like this completely piss me off and the students of this class learned more from the students with pre-knowledge than they did from studying the notes that the teacher gave in the last five minutes of class.

Structure: decades of programming in too many languages to enumerate. I lean functional, but only when the language doesn't fight it. No matter what I'm doing, my code is immutable in practice, if not paradigm.

Syntax: No one thing in particular. I code differently depending on the language.

When I start learning a language, I'll find the standard style checker and create a project where I write an example of every single rule.

The end result is generally a quick intro to the language and a bonus understanding of the hot sports opinion in said language. I call this an ocean boiler.

I lean heavily into autoformatting because I've worked on too many projects to care, and I have a general expectation that something which is important enough to make a code standard is important enough to be enforced in tooling. I'd rather spend my time solving problems that thinking about stylistics.

Why don't devs read the fucking docs?

Time and time again I find my coworkers inventing new ways of doing stuff that could easily be done with existing features.

Today I saw this on a code review (functions are from lodash):

head(filter(...))

That's what fucking `find` does, you dense motherfucker!

This is just a tiny example. I've seen so much of this shit. Sometimes it's almost art how they find ways to solve problems without actually reading the docs.

After solving a lot of problems in codeforces and participating in ACM to make my code the most optimised..
* In my first real job. *
Client: Your program run so fast!! I can't feel if it's doing something or not. Please make a delay of 1 second in your program! 😇
Me: 🙂🙂🙂🙂

Today the IT deparment update the firewall's configuration, they blocked almost every website except email and Google.
The problems:
- Blocked some systems outside the organization, there are in another building and also network
- I can search on Google but I can't see the results outside Google
- Forget about download depencies, libraries, deploy code to outside services, search at StackOverflow

I JUST WANNA SAY GOOD JOB, GUYS

PS: The firewall also block the SSH port, I had explained to my boss and he sent a request for allowing the port, so far no answer

team downloading a library to solve in 12 hours problems I could code myself out in 15 minutes, complication as a service at its best.

I've run into problems with the app I'm working on, the problems are related to issues regarding code.

No in fact it's related the last guy who wrote the app, the code has no comments and the variable names make no sense, the only comments in the code are blocks of code... With no reason as to why it was commented.

I have to add in some checks to determine if a person that has logged in is a full member or not (full member has access to the feature I've added) and the way the guy has made this app works makes no sense to me at all.

I've tried my best to avoid all contact with his code because it makes me want to yell out in frustration.

But for this one case I have to work with what's there.

I know I've mentioned this before but I've hit my limit yet again.

And for those who don't know this guy managed to scrape together skeleton code from two apps to make part of this app, rather than using parts of the other apps he left out code that was specifically made for the other apps, (majority of the commented out code).

One app was a taxi app and from the looks of it the feature he used was to get GPS location (which I don't understand before Google maps is a think after all... The taxi app USES Google maps), the other app is some sort of funeral webcasting app (I found code imports for it, without any actual code).

I don't actual understand how this guy could put this together without not thinking "maybe this is a bad idea"

Always code as if the person who ends up maintaining your code is a violent psychopath who knows where you live

I'm that psychopath right now..... Fuck that guy (don't know where he lives though)

Start changing how young people look at programming. It’s not nerds doing nerdy things, it’s about real people using code to solve real problems. I think once the mindset changes it will get many more people interested.

Why do I have no problems writing code and designing databases, but draw a complete blank when trying to come up with a good database username for the code to use?

> raw http request injected in the model
> 400 lines long method, followed by three 300 lines long methods
> no autocomplete, no comments
> code called by the whole application, I mess up once there's at least 150 other components that might break
> no documentation, no tests
> pyramid of doom, 13 levels of indentation

Those are the same people getting all puffed up because the cat dared to sit on my shoulder during a call. Management focused on the real fucking problems, no doubt.

Story time!

Like I mentioned in a previous rant, I’m (or was) a coca-cola addict. Coca-cola has caffeine, right?

This happened a tuesday. I forgot my mug at home (I wanted to draw it a bat🦇) so I bought a jumbo coffee at a store near my office. I drank it, and then, all my partners went to the kitchen for coffee. I went with them and I refilled my cup.

I was working on my code, and suddenly I felt a strange sensation on my chest (I don’t think I could describe it, it feels like when you have intestinal problems and gases, but in the chest). I didn’t give it importance. One hour later I started trembling. I googled my symptoms and I found I had a coffee overdose 😱 But how? I drank a lot of caffeine in soda, but this only happened to me with coffee. This lasted 5 hours 😓

You, specially the most experienced devs and coffee addicts, how can I drink more than 1 cup of coffe per day without trembling? Btw, I have no heart or pressure problems, so I don’t know... this happened because I don’t drink much coffee?

Your code is supposed to solve the primary problem you have. It is not supposed to create problems and solve those problems you do not have initially.

For me, the worst co-worker is one who works by the principle of quantity over quality or a person who thinks quick and ugly fixes are a valid way to solve problems. Also: If there are unittest, don't fucking dare to change or remove them, just so your code runs without errors.

But in general, I just can't work with people who don't really think about what they are coding, people who just code straight ahead without making the simplest plan about how to solve something. Most of these people realize too late, that their approach was rather shitty, unreadable and unmaintainable.

I often see memes about "I forgot what I coded last [insert timespan here]". Though it is kind of normal, if it takes you too long to find out what you wrote, you should consider overthinking your coding approaches.

Just my 50 cents.

Damn I miss coding... 4 weeks of learning & exams is too long...

Some days you write your code and it all goes well.

All your tests pass, you write clean code, you solve your problems nicely.

Other days everything that can go wrong, will go wrong.

...the latter was the case for me today.

Mirror mirror on the wall, how many code problems do we have overall?

... Im sorry I even asked

Got a simple task

Decided to refactor some related shit so I don't have duplicated code

Get loads of problems with the shit I'm trying to refactor, now I'm late with the simple task

Some fun facts :

☻ Programmers spend approximately 30% of the time surfing the source code 😁

☻ Progress in programming can be classified into 4 stages:
(a). Complex Programming
(b). Making Progress
(c). Slow Progress
(d). Stuck

☻ Programmers have a tendency to report their problems incompletely

☻ The main error messages, execution times and runtime compilation errors and the average time to solve them

☻ The software maintenance consumes more than 50% of the effort

☻ Ctrl C, Ctrl V, and Ctrl-Z have saved more lives than Batman tbh😇

Applied to a Jr. Dev job and was hired as a Digital Marketer — I can deal with this, I’m AdWords & Analytics certified. What I can’t abide is that I spent the last year working my ass off learning to code and the person next to me with the Jr. Dev position only uses DIVI and has zero inclination to study, learn or write basic HTML & CSS—much less PHP. I’m not an expert by any means but I love programming, I love the problem solving, the challenges and the culture of it all. So far, and these are only two examples, I’ve shown him how to use the target attribute to open a page as a new tab, and how to register a nav in the functions.php file to create a menu but he is unwilling to even attempt it. Rather, he told me that I was too technical and that no one would be using code in this day and age.

For the record, I think DIVI is a cool platform, it’s clear that my boss knows nothing about code to be fair and I love my job— this is my only issue so far😂 I just needed to rant.

How come it is so hard to find good developers. Have been doing interviews for a couple of weeks now (for a senior PHP developer role).

First round is me talking about the function and company, asking questions about candidates experience, wishes and we usually end in some tech conversations. Most of the resumes I got are pretty fucking good. I mean, experience with low-level languages, experience with the problems we need to solve here, contributions to open-source, experience in R and MathLab etc etc. On paper they look perfect.

For the second round I give them an assessment which they can do at home on their own machine in their own time. It's not a hard one, just some mathmatical problems they need to solve. A quick google GIVES the answer (no joke!!). But that's OK, I look at their code cleanliness, proper use of commenting so I can determine if they are solo-developers or fit good in a team and if they abstract repeated functions and make sure that they take their work seriously, you know the drill.

It pisses me off that I get BROKEN FUCKING CODE WHICH DOES NOT EVEN RUN and that I get code back which I look at and makes me vomit instantly, I mean, DO YOU EVEN TAKE YOUR PROFESSION SERIOUS? How dare you to ask for 50k the year, a lease-car, extra bonusses AND YOUR FUCKING CODE SPITS OUT COMPLETLY WRONG ANSWERS OR DOES NOT EVEN RUN WHAT THE FUCK DUDE GO BACK TO FROM WHICH EVER HOLE YOU CRAWLED OUT AND STOP WASTING OTHER PEOPLES TIME WITH YOUR FUCKING INCOMPENTENCE...

Writing a super extensive project in php. Twice so far, I have had weird problems of codes not working.

But everytime I copy/paste the SAME code from another file, IT MIRACULOUSLY WORKS!!!!

WHAT THE ACTUAL FUCK!!!

I like to joke around when I am working. I understand that it's not everyone's cup of tea, but ffs you should be able to laugh at really complex problems in stressful situations. How else can you remain sane writing thousands of lines of code just for an e-commerce site or so someone can post even more cat pictures on the Internet.

If you can't laugh and enjoy what you are doing, you might want to rethink what you are doing with your life.

Yes, my Python scripts are not remotely pretty. But then, neither was my nonexistent formal training in scientific computing. And no, I will not 'write two lines of comments for every line of code'. Physics major programmer problems.

I would appreciate if teachers brought in developers that actually work in real projects writing code to show us what they do and how they solve problems every day.

So I was looking through some old files, looking for some help while I was working on a project and I came across my first codes I wrote in school.
This one time I challenged myself and I tried to write the code a bit.....different. When i ran the code it worked as it should, no problems, then he said:" Show me the code how you did it". I giggled a bit and opened it up. I still remember the expression on his face. He wanted to say something twice but couldn't. Then he just sighed and said, please don't do that again.

Problems with redis... timeout everywhere...

30k READs per minute.

Me : Ok, How much ram are we actually using in redis ?

Metrics : Average : 30 MB

Me ; 30 MB, sure ? not 30 GB ?

Metrics : Nop, 30 MB

Me : fuck you redis then, hey memory cache, are you there ?

Memory cache : Yep, but only for one instance.

Me ok. So from now on you Memory cache is used, and you redis, you just publish messages when key should be delete. Works for you two ?

Memeory cache and redis : Yep, but nothing out of box exists

Me : Fine... I'll code it my selkf witj blackjack and hookers.

Redis : Why do I exist ?

Ask yourself a couple of simple questions:
Do you like to code?
Do you like to learn new things and improve?
Do you like to solve problems and spend hours on a single detail until it finally works?

If your answers contain a "no", then development is probably not for you. You will hate it and you will suck at it. And you will make lifes of devs who actually love it miserable. So do something else.

Today’s lesson in C programming:

DON’T use
system( “clear” );
in Mac OS...
Causes seg Fault in ur program when it is perfectly correct...

What happened was... a friend wanted help with C programming and had written this code... but it was getting seg Fault randomly... just random seg Fault when his code was correct...

I pinpointed the seg Fault to a printf statement but the statement was correct...

Off to search the issue I went, found out that flushing problems can occur in printf if u don’t use \n.
This happens randomly. Thought this might b the reason...
Went to a VM running Arch Linux and tested the code there... worked perfectly. No issues whatsoever.

From a distant memory I remembered some people discussing to never use system( “clear” ); since it causes issues.
Thought to remove that line from code, thinking it wouldn’t make any difference.
Well imagine my shock when the code worked fine after remove that freaking line...

M gonna blame this one on Mac OS since arch had no issues with it 😡😡

Now to find alternative to system( “clear” );

Damm it I spent 4-5 hours on this crap!!!!!!

My fav interview was at my previous job. It was a junior position. The lead was a very friendly and wise guy. He kept pushing me (positively) with subtle hint until I get a code right. After completing each problem he give me elaborate explanation about the meaning of the problem and how to approach it from other angles. It felt like I'm in front of buddha who is making me realize the inner working of the world. Didn’t get 50% of the questions right, still he recruited me because "You were very curious and you were having fun solving problems". Best one and half years of my career.

In my three years experience so far I can honestly say that 100% of the developers I've worked with are narrow sighted with regards to how they develop.

As in, they lack the capacity to anticipate multiple scenarios.

They code with one unique scenario in mind and their work ends up not passing tests or generates bugs in production.

Not to say I'm the best at foreseeing every possible scenario, but I at least TRY to anticipate and test my code as much as possible to identify problems and edge cases.

I usually take much more time to complete tasks than my colleagues, but my work usually passes tests and comes back bug free. Whereas my colleagues get applauded for completing tasks quickly but end up spending lots of time fixing up after themselves when tests fail or bugs appear.
Probably more time wasted than if they had done the job correctly from the start. Yet they're considered to be effecient devs because they work "fast".

Frustrating...

So.... yeah, making a Scratch clone (with more features) is frustrating and super hard.

Major problems include
- Drag&Drop from listbox to usercontrol - stress level : 3/10
- connect blocks when two blocks are close to each other - stress level : 10/10
- generate live code when there was a change in blocks editor - stress level : 9/10
- write a compiler or some interpreter that converts block code to real c# code - stress level : 10/10
- generate output by calling csc.exe - stress level : 1/10
- make code at least readable - stress level : 7/10

I've cought a case of "My co-workers copy my code and then get credit for it".

Why in the world IT work is so stressful?
I never been like that since I start developing code professionally, 8 years ago.
Since then, I had many health problems due stress, and some were really scaring (heart problem).

I'm trying to adapt to a healthier way of work, but I'm starting to doubt if that is possible.

Work in technology seems cruel and soulless sometimes. The constant pressure to learn new things all the time, to specialize in a lot of skills, simultaneously. The urgency nature of ALL tasks - even a simple form field slightly out of place seems to be an issue of life and death for clients.

Easy and quick communication made some people lost boundaries and respect. Many times I received calls and messages after midnight, about things like elements alignment.

And the worst is when clients blame you about their business problems. If they are not selling well this week, it's fault of the website you did ( which they are using for months now).

This actually happened to me today, first thing in the morning. After I slept just 3h, because I worked until late yesterday (oh yeah many more of these life/death updates).

What happens in this industry? Will this ever be different some day?

I wish my classmates didn’t know that I’m good at programming.

Recently, more and more often I am being reached out to by my classmates (and especially by one individual) about the problems they’re having issues with. For example yesterday, a guy fucked up his Git commit and made a bunch of merge conflicts, so I helped him fix this, which then lead to WinForms having multiple declarations of same objects.

And I really don’t wanna be rude, and I always try to help, for the love of god - stop bothering me every 5 minutes while I code, or at 10 PM while I wanna chill out.

Most of the things they have problems with can be solved by 2 minute Googling and I strongly believe that at the university level, you should be able to find solutions for your problems yourself - especially when you’re a programmer.

Installed SonarQube and Snyk on the CI/CD of a 2.5 year old project that only had a linter enabled previously.

Practically zero problems found. One minor problem (same code in different branches), a few false positives, and a few possible problems in dependencies that I have no control over.

Now wondering:
Am I really that good or are those tools just shit?

A programmer can code.

A developer is a jack of all trades jumping into any stack and mastering the basics in a weekend.

So why the fuck can't I grasp humans. Their code is spaghetti....
Debugging gives way to many problems...

Atleast my personal code has a feature creep and for once it's a good thing!

I really like this book on the basis of the philosophy overall, no this doesn’t solve all problems but it’s a good baseline of “guidelines/rules” to program by. Good metrics or goals to architect and design software projects high and low level projects.

Fight Software Rot
Avoid duplicate code
Write Flexible, dynamic, adaptable code
Not cargo cult programming and programming by coincidence.
Make robust code, contracts/asserts/exceptions
Test, Test, and TEST again and Continue testing.. this is a big one.. not so much meaning TDD.. but just testing in general never stop trying to break your software.. FIND the bugs.. you should want to find your bugs. Even after releasing code the field continue testing.

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...

Fucking gnu gettext, fucking .po and .mo files and fuck the fucking poedit. Why in the fucking hell a damn i18n solution used by so many languages doesn't support correctly fucking utf 8 characters in strings inside the code, I mean, WHAT THE FUCK, this is my second day trying to make the fucking Python gettext module to translate the fucking word "está" because I've a fucking big code base programming in Spanish that need to be translated. This is the fucking 2016 and we still have problems with fucking special characters? I mean CMMON

When you're alone with your dev problems but still you have the best code partners anyway :D

Jest addin for vscode:
The Good
- I love how it's running all the time testing my code
The Bad
- Doesn't show line numbers where the problems are (may be a babel/promises issue perhaps)
- Doesnt have coloured text (normal jest runner does)
- I can't get debugging working (I'm sure I will eventually)

/rantover

The posts about love coding interviews and low paid freelancing work just reminds me how little anyone know about process of using code to solve real problems.

If someone wanted to give me a JavaScript test then I'd point them at Fivver where there are tonnes of JS devs available for minimum wage.

No one is paying me for my ability to write code. They are paying me to solves problems that businesses have that are likely to involve software.

When code is survival.

Does anyone get the feeling that as they become more senior, they care less about meeting "best practices" and more of just "good enough"?

Best practices being everything in those books about TDD, unit testing, design patterns, design artifacts.

Good enough: enough so it won't blow up in prod, some tests but not 80-90%, some docs. Basically not like those public docs, open source projects/frameworks where function is covered

When I first started professionally, I was all about efficiency, good design, reducing technical debt, clean code.

But now, I look at problems and instinctively I may make these decisions but I don't really think about it much. First goal is to just get something working, clean it up later... Maybe.

Me: Startup initialization tests fail so the system won't boot properly it until we fix those issues.

Manager: comment out the lines of code that are causing problems.

🤔 So we are just going to feed power to some hardware and see what happens I guess

This whole programming profession sucks! Programmers suck! Managers suck! Companies suck! Products suck!

Why is it so hard to organize your stupid code at least a bit?! No, it’s not deadlines, just write a block of code and give it a meaningful name, a function, a method, a comment, so many options, so little fucks given. Give things a meaningful name instead of whatever came to your mind that moment. There’s no excuse! No, just leave it to the next guy, and he’ll leave his trash for another one. And then we complain and make memes about it. Fuck you all!

There’s no purpose or vision of products, managers sweep problems under a rug, executives do whatever they do, as long as some money is pouring in, just keep pedaling semi-mindlessly. Spin the wheel you little hamsters until you drop, there’s enough hamsters out there.

It’s just a clusterfuck of small, selfish interests and egos, a mud of meaningless and unnecessary problems that need not be there.

It’s not the workload, it’s the stress! The stress of bullshit, and constant problems that can be avoided if everyone did their job at least half-professionally. Not just programmers, everyone!

Today I had a client raise a high defect directly with my boss’s boss. I got called into a meeting and was told
I needed to fix it immediately.

I looked and realized it was in their code and not our component. I told them as much. They asked me if I would still fix it. I refused. Told them it’s not my component. Fix your own problems.

Sat their as my boss’s boss asked them how they functioned if they didn’t even understand their own component. Feels good man. All I could do is smile at them trying not to laugh.

-Writes a function that I'm going to schedule for django.
-works in development.
-adds it to production cron using django-crontab
-not working.
-spends 3 hours editing code, searching for similar problems and reading documentations but find nothing wrong and it's still not working.
-maybe it's django-crontab so I decide to just write a custom management command and call it through cron.
-still not working.
-calls function using what I'm telling cron to do.
-everything works.
-?????????
-adds logs to cron command (sorry for not making it earlier)
-mfw the code is not working because I imported 'patterns' in urls.py which has been deprecated since django 1.8

I have ADHD. If you don't know what that means, for me it makes me a better software engineer. I can't do repetitive, so my code is by definition DRY. If someone needs help, I'll notice and help because my brain can't filter out the emotion of someone struggling. I fixate on problems I don't know how to solve, I literally struggle to stop myself. The list goes on. But, at its heart, who gives a shit?

I'm a software engineer, and I'm good at what I do. Does anything else matter?

I got 99 problems and they are all bugs in my code. Then I apply a patch, and I have 112 problems. #devLife

Rewrite of the sync api to REST.

Coworker: “hey, I know you’ve written and maintained our sync module for the past 4 years. Something I need to know? Some hints or knowledge you can share?”
Me: only thing you should not do is x and y. Otherwise you will face problems a and b.”
Coworker: “great, thanks a lot!”

2 months later...

Customer call: “da fuck are you doing? When I do stupid stuff then I face problem z and problem a!!!”

*me checking new code*

*me calling coworker*

Me: “WTF did you do? You asked for my advice and then did exactly what I told you NOT to do.”

Coworker: “oh, let me check the code..”

*coworker calls boss*

Coworker: “Boss, I can’t work with this guy, he starts fights all the time..”

*boss comes to my desk*

Boss: “I don’t want you to work on this anymore, people are complaining.”

Me: “what the fuck, I just asked him a question..”

~ 1 month later

coworker quits because he can’t handle all the bugs he caused and I have to maintain this piece of fucking retard code..

Ran Windows RAM diagnostic tools because I was too lazy to get my Linux USB-stick. Ran for 20 minutes, restarted - "There are hardware problems present."

NO SHIT. No info how many errors, no log file mentioned, no code or anything. Something happened. How retarded can a diagnostic tool be?

Guess laziness gets you punished immediately...

First task as Python delevoper intern - fix non-essential for business app, written by an intern last year. Apparently that intern didn't even know what an object is. In Python, where everything, including functions, is an object.

I have to fix it piece by piece. It would be faster to throw old code and start from scratch.

Yet I'm glad they gave me this task. I feel like I'm learning a lot working with this shitty code. And they assigned a great person to help me should I have any questions/problems.

I could not be happier.

int hairsLostCount = 0;

while(!Code.isWorking){
Code.tryNewUglyFix();
++hairsLostCount;
Console.WriteLine(
"While fixing the code you lost "
+ hairsLostCount
+ " hairs already."
);
}

Coder.doCoffeeBreak();

Steps to becoming one with your code:
1.Get red lamps and make em trippy asf.
2.Syntax color the shit out of your editor.
3.Install activate-power-mode
4.Get high or tipsy
5.Listen to surround psytrance
6.Code

Congratulations you are now in a higher level of existence. You are one with your code and your will is root.

*Disclaimer: Marnsghol is not responsible for any: Injury, death, damage to personal or company property, losing job, getting arrested and/or efficiency problems in work environment. Discretion is advised*

Feeling so dumb right know.
I have a C# exam tomorrow (on paper) and i can't get my brain to think in code.
I can't focus, I can't concentrate. I don't remember things i normally know by heart. Is it just stress? (Everything is pretty hard atm, lots of stress, lots of problems).
What could i do? I'm pretty messed up right now...

To all of us who procrastinate. Here is my new thinking that is making me slightly more productive! I would guess we all agree that the work is fucked up. But what we need to be productive, is an ego big enough to think that we are the only one smart enough to fix it! Just let your ego go!

Why code that project? Because other people would do it wrong! You fuck up the project? Fuck you, do it right or it won't be done right! My internal monologue from now on!

Does this mean I don't ask for help? Of course I ask! So that I can learn it, realise the other person is an idiot, then do it right using their technology!

If you don't do what you are planning to do, nobody will! Also most of the worlds problems can be solved with money, so that is why we should get rich. To fix the problems of the world.

Hope it helps someone :)

make code change

stop server

try to re run server

dependency problems

java, tomcat, gradle , eclipse, just kill me, dont torture me like this

Have you ever argue with a developer who:
+ have the same level as you
+ on the same position in the company
+ in the same team
+ OLDER than you
+ thinks their code is the best

A few years back, a coworker and I argue about how to implement a feature. I proposed an approach. He proposed a different one. I immediately saw some problems and told him. But hell no, he defended his idea so strongly that I just gave up since I will leave the company soon.

2 weeks later, when the sprint was about to end, the whole team had to work overtime to fix the mess because of his terrible approach.

to the guys saying "oop is dumb" / "i don't need oop" / "i've never worked with oop"...

i have some questions:
- which language are you working with
- which problems are you solving
- how big is your code base
- how do you maintain readability of your code?

don't get me wrong, i don't believe that oop is always the answer. i'm just curious which fields these statements are coming from. if they all come from a low level (assembler, C, ..) or functional languages or "scripty" languages (python, JS), or if there are also people working with languages like C++ where oop is pretty much established. and if the latter, i'm curious how people design their code and what problems they solve... tell me your story :D

Wow... I haven't done complex/algorithmic level coding for maybe 6 months (yes that's how mindless my day job usually is)...

Now I just finished part of the code for a scheduling app I'm doing just for fun... Though there is also a use case at work but I don't have the free time to think about problems at this level...

Ahh.. there is nothing like the joyous feeling of writing a working piece of code for your own personal projects.

I spent several weeks and a few hours today to finally get my Python automation script working and I am very proud of myself.

Here's what it does:
* open a text file, extract a specific string from it using rather complicated xpath
* open another text file and do the same
* replace result 1 with result 2
* log results
* close file
* automate the process

Even though it looks easy, I had to mess around with a lot of problems such as permissions, indentation, stream writing, file status, etc.

Now, instead of having to manually do this job, I can just let my machine do it!

Code of developer's life

int f = 1;
If( life == "smooth")
problems();
else if( life =="hard")
{
problems();
breakup();
}
else
{
while (f = 1)
{
bugs();😣
}
}

Hi everyone.
I wish you all a 2017 full of code, of problems to fix, of oportunities to learn new languages and above all full of bugs to fix because from this, is from wherr we learn the most.

No! I don’t have any problems that you are deprecating various libs that I used in my software. Just don’t fucking insist that your code is production ready and stable and backward compatible. Please

Having to use BlueJ makes me want to jump off a bridge. :)

Stupid fucking editor tells me I have errors in my code, even though it compiles without problems using the Java command.

I have 6 years of programming experience, so I'm the go-to guy at my college when someone's Python code doesn't work. The amount of unfathomably obvious problems I've fixed for people makes me wonder if some of my classmates are incapable of reading.

Old pc problems:
Never know if program is slow because
My code is shit
Or my computer is shit

I sometimes cry a lil bit when I see php sql code without pdo. Specially when someone mentions a cool example online or a tutorial or whatever. Guys please, get good with sql as well as pdo....please pretty please with cherries on top. While we are at it, it might not be the solution to aaaall problems....but mvc can do wonders for you, it really can. That pattern has been on for a while...learn it and use it well. Also, restful apis are good mmkay? They fit nice with the glory of Node.js and its amazing front end powers and utilities mmmmmmkay?

I was hired to a working team that is full of experienced people who know how to code but half the team is awfull at solving problems, and all they do is blame each other... why cant they understand we are one team and rather work on solution for 30 minutes they spent deciding who fucked up...

There was a task of fixing up a payments page that features pretty complex logic. Initially it was like 200 lines of code, seems short but it was a fucking spaghetti mess. Never seen more cognitively complex code in my life.

So I delete the spaghetti and pull out the 500 lines fucking state machine. It works perfectly. It’s perfectly understandable even though it’s longer.

This is how I deal with problems. Shorter code isn’t always better code.

<insert obligatory "long time lurker" statement here>

Started a role about 6 months ago. I'm the sole IT programmer. A bit of the mess I inherited...

- 100+ stand-alone applications/tools (luckily most of them aren't too big).
- No documentation.
- Some applications' only copy of the code exists in production.
- We only have production.
- A single file consisting of 30K+ lines of VB. Little to no comments. The one comment at the top says to keep old code by commenting it out and state what you changed.
- Previous devs didn't like foreign keys.
- No. Fucking. Version. Control. At. All.
- And so much more...

Luckily I was hired due to my experience so I could fix all these problems. Its actually a really great job.

I honestly have no problems with UI designers, I really don't and actually respect the work they do..

But god dammit, those fucktards should try designing the UI with actual code rather than photoshop or whatever they use these days..

How to mess with Github Copilot:
1. create open source repo with MIT license
2. create generic functions that solve specific problems
3. put violent, racist, sexist, phobic, political, etc phrases in the code
4. get other people to fork the repo and make their own versions
5. watch as people get upset over copilot being evil and putting shit into their code

Todays rant is about me trying to add some long text into my database. I tried it all day long, but the text was inserted partially all the time. I changed the collumns data type to BLOB, this felt false, but it seemed to work. The bad feeling triggered me to search further, so I rewrote my code and found the source of this behavior. I used utf8-decode-function on my text and that triggered some problems when inserting the text. I don't completely understand it, but I solved the mystery, that fucked up the day. I will sleep good now.

My biggest distraction seems to be when I notice other problems in the code I'm fixing/modifying. I then spend too long putting things right!

Look, normally I don't give a shit how others code, but when the company's style guide is literally just the statement "use eslint", and I have to do code reviews...we will start to have problems.

"This question is unlikely to help any future visitors"

For all the people that answer anyway or answer before this happens, thank you.

To the assholes who do this at SO: I can't tell you how many specific problems I've had where a question that did help me had this.

You all suck. Go fuck yourself off a cliff. The entire site is built on the backs of people who get shat on by a small elitist community that likely couldn't code themselves out of a box.

Again, to those who still answer... thank you. To those who still ask questions in spite of the abuse... thank you.

Not really a rant but more of a fact kinda thing. Noticed a post earlier about someone ranting about why they code figured I'd do the same...

I code not because I wanted to for say but because my after my uncle's death I needed something that I could feel in complete control of. Coding gave me that ability to control the computer however I want and tell it to do whatever however. At the same time it taught me so much more about myself and the people around me in the process. Today I don't code because I need to control something m today I do it because I can't live with out. It forces me to think critically of everything and everyone. It forces me to learn something new everyday and every night. It requires me to solve complex problems with limited solutions. It allows me to create solutions when everything else has failed and it gives me a drive to complete things. It's the reason I live technology and it's the reason I have the job I do. It's the reason my boss loves my work and it's the reason other people on my team envy me. Code transformed my life into what it is today. And it will forever be my greatest peice of education.

I feel like a lot of devs, last years self included.

Need to realize, a great Dev is not necessarily one that Ace in code.

But rather one that can convey and understand the problems they're to solve and more importantly the perspective of the end user.

Proudest bug squash experience?

Fixed a N+1 pattern bug on our web site. Wasn't a deeply technical problem, but I was proud to shove the fix up the arse of the developer who blamed me (and even got a VP involved) for the web site crashes (the N+1 involved his code calling a service I wrote) and none of the half-dozen other devs found it.
I really wanted to make a t-shirt with his initial 'blame' email outlining all the 'technical problems' with my service, and the fix was literally moving the service call outside 5 (yes 5) level deep for..each loops.

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.

Around 6 years ago I started at this company. I was really excited, I read all their docs then I started coding. At every code review, I noticed something was a little off. I seemed to get lots of weird nitpicking about code styling. It was strange, I was using a linter, I read their rules but basically every review was filled with random comments. About 3 months in I noticed, "oh! there aren't actually any rules, people are debating them in my code reviews!" A few more reviews went by and then I commented, "ya I'm not doing any of this, code review isn't a place to have philosophical debates." All hell broke loose! I got a few pissed off developers, and I said, listen I don't care what the rules are, you just need to clearly fucking articulate them and if you want to introduce one, I don't care about that either just don't do it in the middle of my review. I pissed off 1 dev real bad. Me and this dev were working together, the QA person on the team stood up and said "hey! you know what I love about your code reviews?!" The other dev and myself looked at each other kind of nervously, "I love that you're both right, these are all problems!"... 1 year later (and until now) me and the other dev are still friends. Leave it to QA to properly identify the bug.

Me: "Need help with build config problems, please help almighty documentation page!"

Docs Page: "Nah fam, I got 4 headers about problems with no text, a blank code example, and 2 error 404 pages."

And that's why I don't like build pipelines.

Yesterday, I put the final touches on a massive system using hundreds of classes, with thousands of lines of code, all easily maintained because of the way I used abstract classes, and coding to an interface, stubs, etc. And all instantiated with a near english fluent api. With detailed logging and even contacts me when there's problems, result of a year's work. I felt like a genius

Today, this fucking simple contact form that won't do what I want it to for the past 4 hours...

[day 1] my team lead insisted that we work "together" on a story. told me to code my approach while he code his then evaluate both once done.
[day 3] we presented our codes to the team but in the end his code got deployed.
[day 4- 7]we got a lot of defects. we did a lot of fixing
[day 8] undeployed his code then deployed mine.
all problems got solved.

Hi guys!

I never thought that this day will come, be here is my first rant with a big dose of frustration.

So, I'm working on the API team of one of ower products and a coworker that works on the webapp has a lot of problems (don't want to be mean, but he has problems like 'i can't catch a 404 http status, please send a 200 with a message' ) and he always go and wines about the API and that he can't do his job because the API is faulty...

But it is not the case, every functionality of the API is well tested and it works as it should.

So, tonight I was the only one left from my team and the project manager comes and
starts asking me about why I am returning http status codes with all my responses, how the login works and other stuff like that...

Just wasted more than an hour to prove that all the code that I wrote works as expected...

So the library we used to interact with s3 had this very cool delete function. (Pseudocode)

function delete(bucket, file)
request = buildRequest(bucket, file)
sendRequest(request)
OK

Now imagine how many problems we setup without delete permission, because we assumed this librsry actually returns an error code

I don't consider myself a guru in JavaScript (hell I studied theoretical chemistry), but I do hate much of the rationalization behind building a Jenga stack of libraries, frameworks, dependencies... for building everything web related.

Many of the problems I see people solving with these giant stacks could be easily solved understanding how websites work (html, css, js and how interact with each other) with no dependencies giving smaller (for end users at least) and more maintainable code (in the sense it would not require updating dependencies that may be discontinued...)

I do imagine situations where these are ideal... Since there are not absolutes and developing is very context sensitive, but man if I have js article fatigue for ridiculous scenarios.

Let's call her Silvia.

Silvia debugs her code by whispering it out loud: "so if this variable is two, then..."

Everyone thinks Silvia is great. But she asks for help whenever she runs up against the simplest of problems: "I have never worked with this library/dependency before!"
(Well, that's kind of the nature of open source if you ask me.)

Silvia types with superbly heavy fingers, making sure we can hear every keystroke, especially when she hits return.

I think Silvia overcompensates for something.

Who would be interested in reviewing an old peice of Python code I wrote..? It's a few years old, and it uses basic procedual generation to cypher text (entry, or ASCII files) using a hashed password. It's a command line tool.

I used to brag about how "secure" it was, and now I'm curious if it is secure or not.

I plan on picking it back up and open-sourcing it, but I want to know what problems might be wrong with it now.

I am surrounded by incompetent fucking idiots, from the team lead that does a half arsed job at coding and then wonders why nothing further down the chain works to whole component teams that seem to be lagging so far behind they don't even know what the current code base looks like.

And who's in the middle of it all running around fixing all the problems these fucktards create, why yes it's me.

I would leave to let it implode and see what they'd do but I already know, they'd leave it till I got back so I could fix it all for them.

Feel like going around with a rolled up news paper and whacking each of them on the back of the head while screaming "no, bad code monkey, bad, fix your own bugs"

I hate being the go to fix it guy sometimes.

Usual python code problems coming from someone who has been coding in Javascript and PHP (<--no pitchforks please). It's been months already but old habits still keep on coming back
- adding a semi-colon
- mixing spaces with tabs
- using a lowercase boolean
- adding an open brace when declaring a function
- forgetting the colon ( ;'s brother)

Got an assignment last year to use a buffer overflow to "hack" a series of problems within some kind of assembly code. There were 2 required problems, but 6 in total. I completed all 7 (one hidden bonus problem).

The teacher that gave that assignment ended up writing me a letter of recommendation for my masters program

Me using numpy.polyfit() to fit a function to some data. Blame polyfit for not being accurate, search the web to find any related problems, as the polynom doesn't fit at all. Polynom is of 2nd degree, polyfit becomes unstable at about degree 20?? Try Polynomial.fit() ... same results. How can they all be wrong???See a little typo in my code, calculating the polynom points. Fix it, everything works.... wasted 2 and a half weeks because of this error.🤦🤦

!rant

I've always been wondering why do tech companies need everyone to have a strong grasp of algos and data structures?

I've been coding most of my life but didn't get a CS degree so ended up in IT but I kind of want to get into a tech company as my thinking is the quality of code much higher (I spend a lot of time cleaning up other people's code and prod issues over the years...), I've been learning Algo/DS but when I see those technical questions on CareerCup, I go WTF.... it's this the kind of problems you guys do every day?

I know this sounds odd, but I really find algorithms things of delightful beauty.

A creative solution to some very deceptively complex problems.

Sure, some implementations aren't the best, but seeing them after just makes me appreciate the time and effort that must have gone into designing things like Merge Sort, Binary Search, Greedy Algorithms, BST, and Dijkstra's Algorithm.

So! If your code is unoptimal, looks terrible, or is a sheer abomination, take a moment to appreciate the little piece of art you've made before you go and make it better.

When I started this job 4 months ago, I was given a grace period of a week to "get into the groove of the code". I asked the lead dev where on pulse (intranet) the documentation was, he laughed and then resumed what he was doing. I shrugged it off and continued scrolling through the code.
A week later, working on a story, I'm stuck at why a particular function exists. I say "it would be nice if there was documentation, where is that anyway?". Lead dev replies, "one thing you should know about this company, there is no documentation unless it's API related".
Last month's retro, 80% of our (mine and lead dev) problems were related to a lack of kt, I laughed.

Code in such a way that it solves family of problems! Not just one 🙌🏼

When McDonald's janitors are writing code...

Dev1: *creates a MR*
Code: for each HTTP request do

// stuff
Executors.newFixedThreadPool(validators.size()); // effectively meaning will start 7 new threads for each incoming request
// other stuff

Dev2: ^^ ??? Fix that shit. This will cause performance problems.

Dev1: *updates the code*
Code:

// stuff
int THREAD_NUMBER = 10;
Executors.newFixedThreadPool(THREAD_NUMBER);
// other stuff

Everyone: 🤦‍♂️🤦‍♂️🤦‍♂️🤦‍♂️

Can I BE facepalming any more?

Dev Confession:
I wrote a bunch of code today that created more problems than it solved. I did not commit it. I used git stash to hide it. It took me hours to write. I didn't do a test on a small section of code beforehand. Literally hours of wasted man hours.

At least I didn't commit this garbage into the repo. The approach was fine, but the architecture made it a non-solution. Now I need to redesign this code or leave as is. It is production code I cannot just "change" on a whim.

I have officially dubbed this week as confession week. This should be a world wide thing. People should fess up to their terrible deeds. Lets start a trend and confess to our misdeeds in code and life. Make the world a better place!

What do you say?

Just make a program that spits out random strings, run it as code and see if it compiles. If not, repeat. That way, just like the apes typewriter thing, you find the most amazing code that is so complicated, nobody would have thought of, but it solves all of humanities problems, especially the power problem you created by running this code 1000000000000000000000 times parallel.

I've been writing unit tests for an existing project for a couple of months now. I'm not experienced at automated tests, so I'm not sure what's good unit tests supposed to be, but the unit tests that I wrote basically just confirm the flow that already implemented, which to my limited understanding of unit tests is supposed to be the other way around. The good thing is that I could catch some minor problems with the implementation such as not imported class used, the wrong variable used since the project is a rewrite of legacy code so a lot of copy-pasta, I also have to wrap some part of the code that interacts with the filesystem in a DI class so I could test that part.

Computer programming teacher wanted us to write some pseudocode to solve an algorithm just so we can practice writing some code and solving problems. The teacher needs a copy so I spent about 2 hours today rewriting all of that pseudocode because she wants it handwritten...

I really resent people who reduce the occupation to tickets. Our world is just tickets, tickets all the way down.

"well the ticket just says this, but that's vague, so what should I do?"

You either ask for clarification, or you get creative with the blank canvas you were handed.

"well that edge case wasn't called out in the ticket's specs"

this is _why_ we do TDD - to design our code to be able to function as expected for ALL cases

"is there a ticket to refactor that?"

what?! no, it's your job to always leave code better than when you found it (within scope/reason of course)

FFS we are not hired to be code monkeys or glorified typists. There should be joy that comes from getting to be more clever than the average bear and to solve problems and improve things with your code and logic.

shit bums me out.

My day today:
- tell everyone to fuck off and are idiots politely from 10 to 4
- tell them if they won’t fuck off now I will start looking for a job - 1 hour
- listening them apologizing me - 1 hour
- code and solve problems - 1 hour

Mondays

Hopefully I start working on Tuesday.

Learning to code is like learning to write when you were younger. It can be sloppy or clean but if you keep at it it'll probably become clean. But, with these sites like code academy that accept only one solution to the problems they present it's as though you're being told that everything you're doing is wrong eventhough you get a solution to the problem in the end. It bugs me that these sites want people to code the exact same way.

Sometimes I get so excited about doing something that I'm genuinely happy. But when the initial high fades and I'm ten layers of complex code problems deep I always remember how useless I really am

Oh but this time it's gonna be different.
yeah right

Coworker renamed constants in repo for her own code and left for 3 weeks... Even told me she replaced and fixed everything!

Unfortunately the renaming got together with a different functionality and have to rework every part where it's used next week...
Just one out of many problems at my work...
Fucking sucks...

Hi developers.... so i just feel like posting this post

I'm a self-taught developer its been 6 years now and i managed to get myself a job this year at a tech startup and they actually developed this developer department just for me..... with the promise that if i manage to get this department up and running I'll get a higher position as the company grows

So it's been 4 months now and i think i'm doing exceptionally well as a developer since I'm the only developer in that organization..... and some how I feel like if i use my problem solving skills to work on other real world problems not just code and designing systems..... like bringing solutions to real none code related problems i could actually achieve more and make a big difference

but I'm actually learning a lot and hope i'll become more and do more within this organization and grab that top position role

I love learning by doing.

Building MVPs and prototypes is the best way. Even better if you have a chance to show and share them in front of an audience (peer pressure can be good!).

Share the lessons you've learned and what you've done wrong, it will help many more people than just yourself.

I've been working for an eLearning company for the last 4 years (CloudAcademy.com) and I'm in love with the idea of learning something new every day. And not just coding. Code is "only" a tool to solve problems, and learning something about those problems and fields will make you a better developer.

It's now. The last few months. I'm starting to think I might have to leave developer's career [fucking broken messenger heads.. Made me post this rant prematurely]. I'm starting to feel that I have so much more to offer than just write code, solve minor problems by moving miniature blocks here and there.

As for now I've moved to Performance Engineers. Will see how that turns out. But I have a feeling I won't feel like staying there for long either.

Rant/Love.

I am sitting in this Big data class next to a girl.(I don't really talk to her so much but things are about to change ) A guy is asking her to share her code base for some insights/ideas on homework and she advices

Don't look at the code base else you'll get same ideas I got and would never come with an original solution. Then she further goes on advising on solving map reduce problems and giving me some tips to be careful about.

I turned amazed. It was like deja vu. I said the same thing to my friend some time last week.
My eyes glittered and suddenly I am like

Where were you all these days ???

Nothing is more attracting then a girl talking about code.

Am I the only one ??

When I cannot sleep or when I'm half asleep I always think "in programming code". Like if my daily problems or issues where actual classes and methods I need to fix or implement.

This is super weird and I cannot do anything against it. I'm wondering if I am the only one who does this.

Passive aggressive coworkers that have problems with each others work but instead of working out problems together they just complain about each other to me and try to drag me into it. What makes people think I want to play office politic games with them? I'm just there to code!

I left for a week and someone deployed my code to production after being completely tested by qa on a Friday night. I get into the office after being gone for a week and am told that production has been down for many customers for several days. In a panic I start troubleshooting my code with the "What the fuck did I do wrong" face.

Development and qa were in a frenzy to figure out what happened, several developers were trying to figure out what went wrong by tracing through the source code for days, fucking days!

In that while time Noone thought to roll back the code. So, I was in a bind and thought "might as well get a box". Before that I looked at the deployment instructions: only the dll's were pushed, no db or resource file changes were pushed. In 20 minutes after I got back: no more problems for any customers and everything is working fine.

SMDH.

At least I found this picture of turtles wearing raspberries.

>be me
>drinks coffee daily
>goes a day without drinking it, tries to code
>has problems focusing & getting things done
>has trouble staying awake

Never code without drinking coffee
My face when I had 15 errors in 40 lines of code

Anyone else having their imaginary Project manager for your private projects, you do talk to when their are problems with the code?

$git checkout master
error: pathspec 'master' did not match any file(s) known to git

Companies moving away from words like blacklist, master-slave are going to spend developer resources on doing this.

What kind of sensetive idiots have we become that we are wasting productive time? Not that we could be cracking quantum theory problems in that time, but still, seriously!

What's next? Update the dictionary and remove all words ?

And don't comment that I'm insensitive to atrocities. I understand atrocities over race/gender (I come from a brown country, face racism everyday) but how does spending time on updating code bases help?

I know this topic is tired and this isn't supposed to be a pure "REEEE SPACES BAD" kinda rant but I still don't understand why people would ever use spaces over tabs for indentation. I'm genuinely curious so please give me your arguments in favor of spaces because I just don't understand

So here's my position:
Tabs are objectively better than spaces in every single way
(I know that IDEs also do some of these for spaces, more on that later)
1. They are typed with one key press
2. They can be removed with one keypress
3. They allow for individually configurable width (some people prefer 2 and some 4 width)
4. They take up less memory (kinda irrelevant, but still)
5. You can properly navigate your code using the arrow keys which is much faster than using the mouse while typing
6. You don't have problems with accidentially having one too much or one too little
7. You don't have problems when copy pasting or moving code around (e.g. refactoring)
8. Code is much easier to select with the mouse, and
9. it's much easier clicking the right spot with the mouse where you want to continue typing, which is often at the start of a line

Apart from specific alignment, where spaces are fine (but which also almost never comes up), I just can't see a single thing where spaces are better at. So much so that most IDEs have to *pretend* that they're tabs when typing and removing them. It's so ironic yet people still defend it and big companies still use them.

I feel like I'm going mad 😨

Note: this is a joke, it's not code related.

Someone goes to a restaurant, and he asks what they got, and the reply to him: "we have a crochet leg, a chopped liver and ligaments"

He says back: "don't tell me about your problems" XD

My company ex-IT Maintainer, left a long automation script in c++, bit of python 2, and bash for our server which developed long before i went to junior high school. and now, the system is outdated, and have a compability problems. so i got task to give it a fix.

when i opened the source code up. i was like; holy shit who the hell write a code especially c++ all aligned to the left, Yes All of it, not a single line are indented. but in the other side the code seems maintainable, and after autoformat, autoindent and couple of fix later, it was readable. I am just wondering who the hell in the world write a code with a style like that ???? i knew he was aware of code style and indentation since he wrote couple of python scripts. Unbelievable.

sadly i cannot show you the pict cuz of company things.

I'll never understand how you could learn to code by reading the documentation and not by actually...idk...solving problems and coding? Especially if you're a beginner.

Tldr; Do not go to the bathroom when you are stuck on a problem.

Most of you will know that when you are stuck on a problem for a while, that it is worth to take a break to look at the problem with a fresh pair of eyes.

It's good advice and I have been doing it for years, however now I have developed a problem with it.....

I don't drink coffee or tea often so when I'm stuck I always take a bathroom break and most of the time an Idea will pop into my head how to solve the problem.

The problem now is that everytime when I am even a little bit stuck I need to go to the bathroom even when I just went.

It's really annoying because now I need to find something else to use as a break because my brain has associate being stuck with needing to go to the bathroom.

It's probably not a good idea to take a coffee break instead because if my brain starts to associate that I will be a coffee addict in no time.... Haha

Do any of you have a good suggestion to use as a break?

Does anyone watch the movie The Mack (1973)?

Today I am working with some legacy code written by a shitty developer who isn't with us anymore. Every time I make a change the code screams at me with problems.

Every error makes me feel like saying this quote from Goldie the pimp...

"List to me and listen good. I don't give a shit what happened to you!.......get back out there and get me my money!"

Tl;dr I am incredibly ashamed of my code at work.

I recently started working as a junior dev. I know many aspects of the stack I use, and I feel pretty comfortable when solving simple and specific problems.

But this is the first complete project I make, and I received no peer review until now. And my code sucks.

I tried my best to deliver a good and working code, but it became messy in too many places. Now it's too late to refactor.

Probably I just cannot see the right way of modeling specific situations, I don't feel I should blame the frameworks I'm using, but the point is that my code sucks. Or at least this is how I feel.

I'm going to leave this workplace soon (personal reasons, not related to this topic and/or the company), and I am kinda scared of the shit I'm about to leave to them. It's a very nice environment and they don't deserve this crap. Also I have some other good reasons to worry about this, but I cannot tell them.

My plan is to finish a couple or personal stuff I have to do and then spend as many hours I can on the project trying to finish it asap and make the code better (for now I've been working only 6hr/day).

I'm really thinking that I just suck at this.

A "safe" Ubuntu update decided to fuck with my AMD drivers and after rebooting, a nostalgic black emergency terminal greeted me with some cryptic message containing hex code as if any mortal user could make sense of it.

To add insult to injury, local mirrors don't have 18.04 which makes apt vomit errors during software installation.

How the hell does the most well known distro out there manage to have problems like that?

No code compiles at first attempt after 3 am.

You know what I hate? Git commit messages stating 'fixed tests' or 'fixed docs' or 'fixed integration problems'. You did not fix anything, fuckhead. You updated the code, introducing more bugs as usual. FIXED?! NO, UPDATED! That's what I hate.

One responsibility of our team is general code QA for the entire dev department, DevMgr walks in our area yesterday…
DevMgr: “Has anyone reviewed the new WPF threaded model execution code?”
- everyone on the team responds “no”
DevMgr: “Can we get a review on that code ASAP? If it works as well as the developer said, it’s going to solve the lock up problems users are experiencing and automatic logging of errors.”
DevA: “Well, no amount of code is going to stop users from performing bad searches locking up the user-interface. That code is just a band-aid around the real problem. If the developers would write unit tests first …”
- rant about 5 minutes on unit testing that had nothing to do with why the DevMgr was here
DevB: “Yea, the code probably isn’t written to handle threads correctly. All the threading they’ve done so far is –bleep-”
DevMgr: “Oh, I wasn’t aware of that. Get me the results of the code review and if they don’t have unit tests, delete it from source control and let the developer know it’s not up to our standards.”
OMFG!! You have not even seen the code!
OK, DevA ..what the –bleep- does unit testing have anything to do with the user interface! You know the DevMgr is too dim to understand the separation of concerns. Shut your pompous ‘know-it-all’ mouth.
DevB…what the –bleep- have ever done in WPF? You manage the source control and haven’t written any C# in two years and never, ever written code for any significant project. Take that “handle threads correctly” and shove it up your –bleep-. Pompous –bleep-hole. Go back and watch youtube and read your twitter while the grown-ups get the work done.