Designer: The design is done and approved by you. Set the launch date. We just need to put some code behind it and the shop project is finished.

After the meeting the programmers heard what the designer said to the customer in the meeting.
Programmer: *facepalm*
PM: *facepalm*

Found this in my office this morning

Me and my wife are expecting a son soon, given her situation i was with her to the gynecologist...
He received us but i guess he was embarrased to ask to examine her while i was there, so conversation begins:

Doctor: "So... what do you do?"
Me: "I'm a programmer"
Doctor: "So, when a customer says there is some bug you need to take a look at the code to see whats up"

So yeah... someone compared us with the gynecologist :D
I mean... fiddling with my wifes coochie is one thing, but comparing my code with vaginas is the line i can't cross :D

So this customer wanted me to create an app using Flutter (user and admin), PHP for the backend, so I made one for him . He seems to complain he can't login to the admin account which he called me to registered for him right after the payment and weeks later.

With deeper investigation , I checked the log he drop the table where users authentication is stored and blame me about that. Which I fixed it lately by creating a table back.

Later I visit my account Shopee , he reviewed me as "THE WORST PROGRAMMER "

So I was like WHAT THE FUCK? YOU DROP THE TABLE WHICH LEAD YOU CANT LOGIN AS AN ADMIN AND BLAME FOR THAT?

As a consultant, you get tasked with a variety of stuff. Last few weeks been struggling to maintain an old C++ application that was written by a complete tool of an a$$hole with zero knowledge on how to write maintainable and production quality code. It would hardly run without a crash. First it was a challenge I had to accept, but as I stabilized the code and just fell over even more traps, I had to admit defeat and review my approach.

Rewrite is something I would choose last, but this one ticked all the marks worthy of a rewrite. So, the customer is a very friendly researcher and gladly spent 15 hours with me explaining all the math and concepts - just a delight for a programmer to have such a customer. Two days in, with a DDD approach - a functional, more precise, faster and stable application.

Sometimes there is no rant to share, it's rare to have that perfect communication with a customer that is so dedicated that he spends so much time teaching you his speciality and actually understand your approach. DDD was really a lifesaver here, by using it's key concepts and ubiquitous language. The program is essentially 8000 lines of math, but wrapping it up with value objects and strong domain models made me understand his domain and him mine. It also allowed me to parallelize the computations, giving me a huge performance boost. Textbook approach, there will not be many like this!

Did a bunch more cowboy coding today as I call it (coding in vi on production). Gather 'round kiddies, uncle Logan's got a story fer ya…

First things first, disclaimer: I'm no sysadmin. I respect sysadmins and the work they do, but I'm the first to admit my strengths definitely lie more in writing programs rather than running servers.

Anyhow, I recently inherited someone else's codebase (the story of my profession career, but I digress) and let me tell you this thing has amateur hour written all over it. It's written in PHP and JavaScript by a self-taught programmer who apparently discovered procedural programming and decided there was nothing left to learn and stopped there (no disrespect to self-taught programmers).

I could rant for days about the various problems this codebase has, but today I have a very specific story to tell. A story about errors and logs.

And it all started when I noticed the disk space on our server was gradually decreasing.

So today I logged onto our API server (Ubuntu running Apache/PHP) and did a df -h to check the disk space, and was surprised to see that it had noticeably decreased since the last time I'd checked when everything was running smoothly. But seeing as this server does not store any persistent customer data (we have a separate db server) and purely hosts the stateless API, it should NOT be consuming disk space over time at all.

The only thing I could think of was the logs, but the logs were very quiet, just the odd benign message that was fully expected. Just to be sure I did an ls -Sh to check the size of the logs, and while some of them were a little big, nothing over a few megs. Nothing to account for gigabytes of disk space gradually disappearing.

What could it be? I wondered.

cd ../..
du . | sort --sort=numeric

What's this? 2671132 K in some log folder buried in the api source code? I cd into it and it turns out there are separate PHP log files in there, split up by customer, so that each customer of ours (we have 120) has their own respective error log! (Why??)

Armed with this newfound piece of (still rather unbelievable) evidence I perform a mad scramble to search the codebase for where this extra logging is happening and sure enough I find a custom PHP error handler that is capturing (most) errors and redirecting them to these individualized log files.

Conveniently enough, not ALL errors were being absorbed though, so I still knew the main error_log was working (and any time I explicitly error_logged it would go there, so I was none the wiser that this other error-catching was even happening).

Needless to say I removed the code as quickly as I found it, tail -f'd the error_log and to my dismay it was being absolutely flooded with syntax errors, runtime PHP exceptions, warnings galore, and all sorts of other things.

My jaw almost hit the floor. I've been with this company for 6 months and had no idea these errors were even happening!

The sad thing was how easy to fix all the errors ended up being. Most of them were "undefined index" errors that could have been completely avoided with a simple isset() check, but instead ended up throwing an exception, nullifying any code that came after it.

Anyway kids, the moral of the story is don't split up your log files. It makes absolutely no sense and can end up obscuring easily fixable bugs for half a year or more!

Happy coding.

Programmer: We really have to refactor the codebase!

Director: That's not important. Do you think our customer would care what it looks like under the hood if we are selling cars?

One year after...

VP: We need to build a new platform for flexibility!

Director: Let's rewrite!

After three hours of emailing with a customer I can confirm that programmers are the worst customers.
Customer: We've found a bug in the system... <details>
Me: Thank you for letting us know, a ticket has been created and the issue is most likely to be fixed in the next release.
Customer: Please grant me UPDATE privileges in the live(!) database so I can fix it myself
Me: I cannot allow that. You have to use the client software for maintaining your data.
Customer: No, I don't want to spend my day clicking. I want to write queries.

We didn't reply to the last one yet...
If we give him access, then I would charge them at least 3x for fixing issues caused by him.

Boss:

Here's an email from a customer who has a report that isn't showing the right data.

It pulls from one application that we've never heard of, and communicates with another application that we've never heard of.

The customer fired their IT team years ago, and can't get in touch with them anymore.

You're a programmer, so we're giving you access to their network so you can fix it.

Please hurry.

Full stack programmer on the recruitment post vs reality

Requirements written on the recruitment post: Frontend Development, Backend Development.

Reality: Frontend Development, Backend Development, Devopts, Infrastructure, UI/UX Design, Video Editing, Design, Customer Service...

Me: Full Stack means everything

Conference call with customer:

Me: You want your customers to see orders that YOU cancelled on them? Are you sure about that? Won't that upset some of them?

Customer: Nope we want that.

Me: Uh ok....

-weeks later-

Customer: OMG OUR CUSTOMERS CAN SEE ORDERS WE CANCELLED!!!

ʅ͡͡͡͡͡͡͡͡͡͡͡(Ɵ۝Ө)ʃ͡͡͡͡͡͡͡͡͡͡

Like bro, I'm just the programmer but sometimes we understand things ..... stop and listen for a moment...

!dev

So one of our project allows paying in money in different currenceis, and we have few bank accounts that are "outter shell" that are monitored and properly titled wire transfer will work for paying in for certain customer. Simple. So far.

We also have +- 20-30 different bank accounts for different purposes, I dont rly know why. Im just a programmer here. Anyway, I have no idea how and why but apparently one of our partners somehow put his hands on list of our bank acc's. Welp, i should be allright, what can possibly go wronggg.... wait... what?

He had this brilliant idea to streamline more process of "go to app, press button, you will be presented with proper bank acc for you". So he did. He sent mass email to all his customers that here are all bank acc's, use wahtever to pay in. Most of acc's are unmonitored.

This went wrong and we figured out becouse mail of pissed customer....

Congratulations, my friend. You earned "I am idiot" tatoo on forehead. Visit me to redeem your reward.

This fucking guy create a mess of a code, more than a spaghetti code, a clusterfuck of shit untested spaghetti code, and the project is actually getting well, our customer is getting bigger but everytime there is something to be added, its a fucking pain to add, and when something breaks, almost every thin breaks, and the shitty guy who wrote this code is quitting and its fucking up to me to clean up all the fucking mess, fucking asshole.

DOCUMENT AND TEST YOUR CODE KID, DONT BE A FUCKING SPAGHETTI PROGRAMMER

Programmer like working at night (at least I like working at night). Would it be cool if there is a company which the work hour will start at midnight and end at early morning?
Customer facing side of the company can work the regular hour while developer will work at night.

I’m currently still looking for a new job after two very, very horrible jobs. My doc said I’m worked out and shouldn’t work for a while because it really has some physical negative effects.

I always feel unenthusiastic, have breathing problems, crumbly, sweaty hands all the time.

But just today the CEO of a company I know from a previous customer texted me on behalf of another company which I’ve worked for where I was extremely happy. Sadly, that company wasn’t quite the focus I had as programmer.

But I’m happy to slowly be known in the industry around me and look positive in the future.

A couple of years ago, I was invited for an interview after applying for a part time job as a C/C++/Assembly developer with customer contact to earn a bit of money while studying at university.
Throughout the whole interview they didn't ask me a single question related to the work I was expecting to do. Just a couple of questions about my team skills, how I would react in certain difficult situations and how my studies were going. Nevertheless they seemed pretty pleased with me and asked when I could start.
I was somewhat irritated by that, especially because I was still a beginner in some areas and made that quite explicit in my application. I asked what kind of projects I would be working on and what skill level was expected of me.
"It's pretty straightforward. Just pick up the phone and go through the checklists we'll provide. You'll pick it up quickly."

Wait what?!

Turns out they didn't have an opening for a programmer. They were looking for somebody for a first level phone support minimum wage job and simply used an old ad for a programmer's position "to attract more technically minded people".

I rejected respectfully...

What the actual fuck? Who even does something like that?

I currently work on a legacy system for a company. The system is really old - and although I was hired as a programmer, my job is pretty much glorified data entry. To summarise, I get a bunch of requirements, which is literally just lots of data for each month on spreadsheets and I have to configure the system to make it work, which is basically just writing a whole bunch of SQL scripts.

It’s not quite as simple as that, because whoever wrote the system originally really wrote it backwards, and in fact, the analysts who create the spreadsheets actually spend a fair bit of time verifying my work because the process is so tedious that it’s easy to make a mistake.

As you can guess, it is pretty much the most boring job ever. However, it’s a full time job with decent pay, and I work remotely so I can stay home with my son.

So I’ve been doing it for about 18 months and in that time, I’ve basically figured out all the traps to the point where I’ve actually written a program which for the past 6 months has been just doing the whole thing for me. So what used to take the last guy like a month, now takes maybe 10 minutes to clean the spreadsheet and run it through the program.

Now the problem is, do I tell them? If I tell them, they will probably just take the program and get rid of me. This isn’t like a company with tons of IT work - they have a legacy system where they keep all their customer data since forever, and they just need someone to maintain it. At the same time, it doesn’t feel like I’m doing the right thing. I mean, right now, once I get the specs, I run it through my program - then every week or so, I tell them I’ve completed some part of it and get them to test it. I even insert a few bugs here and there to make it look like it’s been generated by a human.

There might be amendments to the spec and corresponding though email etc, but overall, I spend probably 1-2 hours per week on my job for which I am getting a full time wage.

I really enjoy the free time but would it be unethical to continue with this arrangement without mentioning anything? It’s not like I’m cheating the company. The company has never indicated they’re dissatisfied with my performance and in fact, are getting exactly what they want from employing me.

Was an internal auditor translating department process to a technical spec for a programmer. We were going to leverage an external company's API which would replace our need to use their slow and buggy web app.

During a meeting, an audit teammate suggested something be changed with the external service we were using. I said we could bring it up with the company but we shouldn't rely on it because we were a small customer even during out busiest month (200 from us vs 10000+ from big banks).

Teammate said we should have our programming team fix it. I made it clear that it was not our side and that to build out the service on our side was beyond our scope. Teammate continued to bring it up during the meeting then went back to desk after meeting and emailed us all marked up screenshots of the feature.

I ignored this and finished writing up the specs, sending them over to the programmer building out the service.

30 minutes later I get a call from programmer's manager who was quite angry at an expanded scope that was impossible (engineers were king at this company. Best not to anger them). Turns out my teammate had emailed his own spec to the programmers full of impossible features that did not reference the API docs.

I feel bad about it now but I yelled at my teammate quite loudly. I said he was spending time on something that was not reasonable or possible and when they continued to talk about their feature I yelled even louder.

Didn't get fired but it definitely tagged me as an asshole until I left. Fair enough :)

Bugs: These are not bed bugs. For programmer they are a nightmare, to customer we introduce them as a new feature and say, “My software has no bug. It just develops random features.”