Me: GET /sleep
Baby: 307 Temporary Redirect
Baby: 204 No Content
Me: 200 OK

Me: GET /sleep
Baby: 307 Temporary Redirect
Baby: 413 Payload Too Large
Me: 102 Processing
Me: 200 OK

Me: GET /sleep
Baby: 307 Temporary Redirect
Baby: 444 Connection Closed Without Response
Me: 200 OK

Me: GET /sleep
Baby: 307 Temporary Redirect
Baby: 444 Connection Closed Without Response
Me: 429 Too Many Requests

Me: GET /sleep
Baby: 307 Temporary Redirect
Me: 101 Switching Protocols
Me: 408 Request Timeout
GF: 102 Processing

Me: GET /sleep
Sleep: 404 Not Found
Me: 406 Not Acceptable

(Morning)
Me: 501 Not Implemented

Dev: this task is done, can I put it in review and do something else?

Me: sure, of course.

Dev: cool, just be aware I'll make some changes to it later.

Me: ... wait, then it's not done.

Dev: no it is, I just need to re-read it and make some changes.

Me: yeah, so it will be done when those changes are made.

Dev: but I don't know what those changes are.

Me: ... I get that ... but ... ok I'm extremely confused. Why do you think it's done.

Dev: because I've written everything I need to and I'm happy with it.

Me: ok so why do you want to make changes.

Dev: I don't.

Me: ... ... ... ... you ... you are really not being clear. If you don't want to make changes, and you are happy with it, why are you planning on making changes later ... after marking the task as done.

Dev: well if I re-read it and see something I don't like, I would like to change it.

Me: ok, so re-read it as many times as you like and make as many changes as you like. But don't mark it as done until it is done.

Dev: but it is done.

Me: no it's not.

Dev: it is, look.

Me: ... yeah looks ok at a quick glance.

Dev: ok so I can mark it as done?

Me: are you going to make more changes?

Dev: yes.

Me: then no.

Dev: why?

Me: BECAUSE ITS NOT DONE.

Dev: ok maybe I'm not explaining it clearly.

Me: ... we can both agree on that. Ok so to summarise, we don't mark something as done until we have stopped touching it. We don't half finish something and say it's done and comeback to it later. We mark it as done when we are happy with i.....

Dev: but I am happ.....

Me: *raises hand* I repeat, if it's done, we lock it away and stop touching it. If someone reads it and complains, we can come back to it with a new ticket. But it's not done until we think we are ready to send it on.

Dev: I am ready to send it, I just may want to change it.

Me: ... ... ... ... ... due to a new policy implemented just now, we are only allowed to send 1 email to a person each week. So unfortunately we can only send on 1 copy. So when you have that 1 copy, let me know.

Dev: ok, let me re-read it a few more times then.

Me: there you go.

Client: I know other developers who would do the same and much more for much less.

Me: I am glad you chose to work with me instead.

Client: I mean I like the site but I still feel that the development process has taken longer than it should have.

Me: Well, it is within the time frame I had said I would be able to have the first version of the site running. I have also implemented quite a number of new features that we had not earlier agreed on.

Client: I think I'll pay (quotes less than 20% of the total cost ).

Me: That is less than the amount that you were to pay as the first instalment ages ago!!

Client: I mean I like the site, but I think it still lacks the X factor. I want ...*goes on to mention other features*

Me: While I take pride in making my clients happy, I believe this process should be mutually beneficial. You are constantly making requests for new features but are making no attempts to meet your end of the agreement.

Client: FYI, there are people begging me for this job.

Me: *Takes down the site.* I wish you all the best, I hope the other developers are up to your standards.

Client: *Literally ignoring the fact that I just quit*. I want (makes more requests).

I am simply going to ignore this one!!!!

Big client, sells products in 30+ countries.

Tries to generate newsletter subscribers, so asks for a system to send a coupon upon subscription.

2 days later, client calls in panic. “We have too many subscribers, our marketeers say it’s a bot issue, can you do something?”.

Checked the data, checked analytics, turns out there’s a lot of referral traffic from freebie-sites, no sign from a bot issue.

Called the client back, “sorry, but there’s nothing you can do about that, you wanted your newsletter to become popular. Not you’re the victim of your own success”.

Client: “can we add captcha?”

Me: “why would you want to do that? You don’t even have a bot issue”

Client: “to make it harder for people to subscribe”

I tried to talk som sense in their heads, but after 3 times I gave up and implemented the damn captcha. It’s still there, doing nothing but annoying thousands of people, including me...

Dear nerds from all over the world,
We get it. 404 pics are funny.

But did you know there other status codes too?
Like...
204 - No Response
301 - Moved
302 - Found
400 - Bad request
401 - Unauthorized
402 - Payment Required
403 - Forbidden
501 - Not Implemented
502 - Service Temporarily Overloaded

I'm sure you'll also find funny situations with these.
Thanks. We're the best!

So I have implemented all the features required for the current release. Carefully reviewed my code several times, but no testing.

Tester: everything passed green. Not sure whether you're a good dev or I'm a bad tester.

Me: let's call it a draw.

Holy fucking shit.

Why do people always expect you to know absolutely everything the second they ask?!

PM: "Yes yes of course we can do that!!! We've done it a million times, we do it for breakfast HAHAHAHAHA"

ME: "Well not really, we've never implemented a solution like that one, its gonna take some time to figure it out"

PM: "HAAAAHAHAHA HE'S SOO FUNNYY LMAOFUDKSJ DONT WORRY WELL HAVE IT READY FOR TOMMORROW :P".

Holy fuuuck I understand you wanna make the sell but you need to give the costumer a realistic look at things, at least give a reasonable deadline for what he's asking! FFS ASK ME HOW COMPLICATED ARE THE THINGS HES ASKING FOR BEFORE TELLING HIM WHEN THEY'RE GONNA BE READY! MAKE A FUCKING ESTIMATE, WE'RE SUPPOSED TO BE A TEAM!

Oh and this rant is gonna happen, dont care if I get fired.This needs to change.

Languages without a fully implemented type system.

Granted, it has been a fad for a quarter century, but everything points at one simple fact: Types matter in programming.

In dynamic languages, you tend to see that testing suites explode into thousands of tests, many of which wouldn't even be necessary if you had some type safety.

You see that languages like JS are forked into more typesafe dialects, like Typescript. Python got typehints since 3.6, and PHP added typehints for methods, then typehints for properties, and will soon even have compound types.

Maybe most languages will never reach the level of Haskell or Scala, and that's totally fine, but I think the direction languages are moving in is pretty much set in stone: No ambiguity, more safety. Code should fail before deploying, not after.

So I got an answer on Stack overflow

Answerer basically said "finding the error is tedious so I re-wrote your code"

They changed about 15 lines in their answer. I combed over it and found that I needed just one.

I put an answer myself, saying which line was missing (as the other answer didn't highlight the actual solution, and rather re-implemented my code)

My clear, concise answer was deleted by moderator for "Not adding anything new" (Except what the exact answer was to my problem, I guess)

Not my fucking problem. Make your own Q&A site harder to use, as if I give a fuck.

Smart India Hackathon: Horrible experience
Background:- Our task was to do load forecasting for a given area. Hourly energy consumption data for past 5 years was given to us.

One government official asks the following questions:-
1. Why are you using deep learning for the project? Why are you not doing data analysis?
2. Which neural network "algorithm" you are using? He wanted to ask which model we are using, but he didn't have a single clue about Neural Networks.

3. Why are you using libraries? Why not your own code?

Here comes the biggest one,

4. Why haven't you developed your own "algorithm" (again, he meant model)? All you have done is used sone library. Where is "novelty" in your project?

I just want to say that if you don't know anything about ML/AI, then don't comment anything about it. And worst thing was, he was not ready to accept the fact that for capturing temporal dependencies where underlying probability distribution ia unknown, deep learning performs much better than traditional data analysis techniques.
After hearing his first question, second one was not a surprise for us. We were expecting something like that. For a few moments, we were speechless. Then one of us started by showing neural network architecture. But after some time, he rudely repeated the same question, "where is the algorithm". We told him every fucking thing used in the project, ranging from RMSprop optimizer to Backpropagation through time algorithm to mean squared loss error function.

Then very calmly, he asked third question, why are you using libraries? That moron wanted us to write a whole fucking optimized library. We were speechless at this question. Finally, one of us told him the "obvious" answer. We were completely demotivated. But it didnt end here. The real question was waiting. At the end, after listening to all of us, he dropped the final bomb, WHY HAVE YOU USED A NEURAL NETWORK "ALGORITHM" WHICH HAS ALREADY BEEN IMPLEMENTED? WHY DIDN'T YOU MAKE YOU OWN "ALGORITHM"? We again stated the obvious answer that it takes atleast an year or two of continuous hardwork to develop a state of art algorithm, that too when gou build it on top of some existing "algorithm". After listening to this, he left. His final response was "Try to make a new "algorithm"".

Needless to say, we were completely demotivated after this evaluation. We all had worked too hard for this. And we had ability to explain each and every part of the project intuitively and mathematically, but he was not even ready to listen.
Now, all of us are sitting aimlessly, waiting for Hackathon to end.😢😢😢😢😢

At one of my former jobs, I had a four-day-week. I remember once being called on my free Friday by an agitated colleague of mine arguing that I crashed the entire application on the staging environment and I shall fix it that very day.

I refused. It was my free day after all and I had made plans. Yet I told him: OK, I take a look at it in Sunday and see what all the fuzz is all about. Because I honestly could fathom what big issue I could have caused.

On that Sunday, I realized that the feature I implemented worked as expected. And it took me two minutes to realize the problem: It was a minor thing, as it so often is: If the user was not logged in, instead of a user object, null got passed somewhere and boom -- 500 error screen. Some older feature broke due to some of my changes and I never noticed it as while I was developing I was always in a logged in state and I never bothered to test that feature as I assumed it working. Only my boss was not logged in when testing on the stage environment, and so he ran into it.

So what really pushed my buttons was:

It was not a bug. It was a regression.

Why is that distinction important?

My boss tried to guilt me into admitting that I did not deliver quality software. Yet he was the one explicitly forbidding me to write tests for that software. Well, this is what you get then! You pay in the long run by strange bugs, hotfixes, and annoyed developers. I salute you! :/

Yet I did not fix the bug right away. I could have. It would have just taken me just another two minutes again. Yet for once, instead of doing it quickly, I did it right: I, albeit unfamiliar with writing tests, searched for a way to write a test for that case. It came not easy for me as I was not accustomed to writing tests, and the solution I came up with a functional test not that ideal, as it required certain content to be in the database. But in the end, it worked good enough: I had a failing test. And then I made it pass again. That made the whole ordeal worthwhile to me. (Also the realization that that very Sunday, alone in that office, was one of the most productive since a long while really made me reflect my job choice.)

At the following Monday I just entered the office for the stand-up to declare that I fixed the regression and that I won't take responsibility for that crash on the staging environment. If you don't let me write test, don't expect me to test the entire application again and again. I don't want to ensure that the existing software doesn't break. That's what tests are for. Don't try to blame me for not having tests on critical infrastructure. And that's all I did on Monday. I have a policy to not do long hours, and when I do due to an "emergency", I will get my free time back another day. And so I went home that Monday right after the stand-up.

Do I even need to spell it out that I made a requirement for my next job to have a culture that requires testing? I did, and never looked back and I grew a lot as a developer.

I have familiarized myself with both the wonderful world of unit and acceptance testing. And deploying suddenly becomes cheap and easy. Sure, there sometimes are problems. But almost always they are related to infrastructure and not the underlying code base. (And yeah, sometimes you have randomly failing tests, but that's for another rant.)

Job offer:

"There is no hierarchy within this company."

Bullshit.

Given a group of people, a hierarchy will emerge. In any company, a hierarchy will emerge. Even within a team a hierarchy will emerge.

Some people like to butt heads, some people like to go with the flow. It's how you deal with these personalities that matters.

You can try to be as fancy you want and declare your hierarchy to be as flat as a pancake, yet the reality is: there will be one.

Certain people will be trusted more by other people. Certain people will have more power in the decision making process.

Can we please stop deluding ourselves that this is not the case?

And that is not necessarily a bad thing. It only becomes bad if the company culture sucks. Instead of platitudes in regards to the assumed absence of hierarchy, I would be more interested to know how a company deals with its hierarchy.

How is feedback handled? How do people argue? How are decisions made, challenged and implemented?

That's what I would find much more interesting.

I just got handed a legacy php web project... Full of vulnerabilities... And it's using only mysql_ functions... Not only it's not OOP, there is not even a single class...

How good it's coded: User profiles are created manually by the frontend dev as htmls, and then the past php dev implemented them as links etc in the current page.

This is how I feel:

That feeling when your soul dies a little because you implemented it as you were told and not as it should have been.

Infinite loop...

Got a story assigned with no requirements listed this sprint. Since I finished the rest already I was like, lets be pro-active and see what it's about during the stand-up.

Me: Hi, I only have story X remaining, what's it about, there are no requirements listed in Jira?
SM: Yeah person Y is going to reach out to you with the reqs.
Me: Ok, when is Y going to reach out?
SM: Y doesn't have time now, will probably be in 2 weeks.
Me: Ok, so why is the story included in this sprint then?
SM: Because they want X implemented this sprint.
(Me wondering if the Scrum Master is familiar with infinite loops, thinking let's try this out)
Me: Ok, if X should be completed, can Y reach out to me with the requirements?
SM: Y doesn't have time now, will probably be in 2 weeks.
Me: Ok, why is the story included in this sprint then?

Stand-up lasted a lil' longer today... Hope the SM got the message not to assign stories without reqs or clear communication anymore.

Shower Thought :
I wonder, in the future, since people is easily offended by everything, variable naming would be such a concern it'll be seriously implemented in the compiler, and be like
"Error at 16:1 NamingConventionError : 'fuckThis' is not linear with our guidelines"

Stakeholder: There’s a bug on the site.

Me: That’s not a bug. The site is supposed to do that. Your team asked for that feature and we implemented it last summer.

SH: They did?

Me: Yes, they did.

SH: You sure it’s been like this since last summer?

Me: YES!!!

One of our internal customers to my team: "We need this new feature to be implemented as soon as possible! It's super urgent!! Work on it asap!! PEOPLE ARE DYING!!"

Us: "Ok, we'll prioritize this feature and deliver it as soon as we can"

Them: "Is it ready yet?"

Them: "Is it ready yet?"

Them: "Is it ready yet?"

Them: "Is it ready yet?"

... One month later ...

Them: "Is it ready yet?"

Us: "We're done! We implemented everything as promised! Please give us your credentials so that we can whitelist you and you can start using the new service"

Them: "Okay, we will get back to you"

... Two months have passed since then and still not a single word from them. I'm starting to wonder: are they still alive? 🤔

I would kill all these +1 guys, srsly. I subscribe these threads to know if it will be implemented.

You do not add any value to issue:
* devs are pissed off as this does not help solving problem
* others are pissed off

No one really cares about your likes, really.

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

Me
Yeah sure why not.

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

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

FUCKING FUCK! THE TEAM LEAD WANTS ME TO MAKE AN UNNECESSARY UPDATE, AND IN THAT TOO HE WANTS TO IMPLEMENT A HALF ASSED FEATURE. Upon telling him what it takes(which he doesn't understand shit about cuz he's not from webdev background and has the level of experience that I had when I was midway my first webdev book), not to mention that he hasn't even seen the code of the project I've worked upon, which I got from an intern they fired last year cuz of not working and shitting around everywhere in the code(I asked if we could start afresh and he says that it'll take too much time - guess what, it took us two extra weeks already cuz of that and half of our required features can't be implemented cuz the code is beyond any hope), he tells me that "The client won't need this feature, but we're thinking of more and more features to provide (WHAT THE ACTUAL FUCK).
Okay, you wanna sell your product; fine. I suggested that if we're letting the client select the time stamp on the initial date, then we should let him select the time stamp on the ending date too, right?
"No, we'll not provide this feature" ARE YOU FUCKING BONKERS?! WHAT THE FUCK IS THE FUCKING PROBLEM WITH YOU?!?!
I'll have to make major breaking changes in the code, for which I'm not the only one working on. Great.
This, coupled with the fact that he speaks unbelievably slow and it's so irritating cuz he repeats himself thrice.

What happens(has already happened), when he'll show this to the seniors, he'll say that this is either unnecessary/will suggest a major change, which WOULD HAVE BEEN MUCH FUCKING BETTER IF TOLD BEFORE I START WITH THE CHANGE, YOU FUCKING CUNTS

I thought this would be fun. Well fuck me.

I was stuck with an architectural problem for a few days. Tried to solve it in many different ways. I could always do a quick hack and call it a day, but.. That's not pretty and it would be a trip wire for future developments.

Went to bed at ~2am. Took a few hours before I finally fell asleep. In my dream I was solving the same problem as in real life, except there I found an obvious and simple solution. Woke up at 8am, repeated that solution to myself a few times to not to forget it. Implemented it in the evening and it worked perfectly!

Moral of the story: do not work late. Better go to sleep, rest your mind. You might solve the problem while resting, and you will need a clear mind in the morning to remember and implement the solution :)

p.S. This happened to me more than once.

Once, at school, last year, we had to present a C# project that, upon clicking a button, took words from a .txt file and showed them in an alphabetical listBox...

Since the file they gave us was so long that we had to wait a minute or so to get the listBox full, I implemented a progressBar which popped up on the button, and upon clicking it, the progressBar advanced for every word it loaded, until, upon finishing, it would have disappear leaving again the button, and the listBox would have been loaded.

Apparently, this choice alone – even if it had next to nothing to do with the exercise – was enough to give me a solid 9 out of 10, because our professors never explained us about progressBars and I used that completely on my own... I tend to do things like this in class, where I explore what my tools could give me.

So long story short, I ended up having the best vote in class for that, and I was so happy and motivated :D

Moral of the story: if you can, always try to learn something new about your tools and your programming language, on your own, because apparently it gives you advantage towards others, at least in school. Or even if you're not in school, it could still be something cool to learn that might be helpful in the future, for your projects or your job's projects.
The more you know, the better!

I think I figured out why so many companies jumped on board the Agile approach. Companies heard Productivity Bonus and Put Stuff into a List Of Things to Do, and left out all the rest of their responsibilities. One of my past companies was like "We're going to take an Agile approach to everything! Except, we're not going to shield developers from everyone who has stuff in the backlog, and we're going to have other meetings during the day on top of the scrum meetings to check on your progress, and we're going to measure points in time instead of complexity".

I feel like the creators of the Agile Manifesto would be really upset at all of the poorly implemented processes. Because all of us developers are pretty upset.

In the begining of time, when The Company was small and The Data could fit in some fucking excel sheets, Those Who Came Before implemented some java tool to issue invoices, notify customers and clear received payments.

Then came the Time Of The Great Expanse, when The Company grew to unthinkable levels. Headcount increased with each passing day, and The Data shows that everything was going great!

But when the future seemed bright, came The Stall-Out. The days when The Company could not expand as fast as it did before. And Those Who Came Before left, abandoning their Undocumented Java Tool to its own luck.

Those who came after knew nothing of the inner workings of the Undocumented Java Tool. They knew only that the magical Jar would take a couple fucking excel spreadsheets and spit out reports and send emails like magic.
And those were The Dark Days.

In the darkness, The Data grew to be a monster. Soon a fucking excel spreadsheet could not hold The Data contained any longer. Those Who Came After, fearing the wrath of The Undocumented Java Tool, dared not mess with its code. Instead, they fucking cut away the lowest volume transactions from the fucking input spreadsheet, and left the company to report the unbilled invoices as "surprise losses". Fucking script kiddies, were Those Who Came After.

Then, at The Darkest of Days (literally, Dec 21st), marched into the project The Six Witchers, who fear not the Demon of Refactoring.

This story is still unfolding. Will The Six Witchers manage to unravel the mysteries of The Undocumented Java Tool? Will they be able to reverse engineer the fucking black box, and scale it's magic into a modern application?
Will they decrease revenue forecasting error by at least 2% in a single strike?

Only the future will tell.

*bunch of if statements*

Friend shouts proudly everywhere : I implemented an AI!

Me : but that's not how AI works

Friend : but it works just as an AI, so it is one, who cares?

😥

How the fuck am I expected to salvage a fucking project that has been handed down to me with.
- No fucking clear architecture
- No fucking documentation
- Fucking shitty ass code base with no fucking coding standards
- The previous team was fucking learning a whole fucking new technology stack *Not fucking kidding* making fucking mistakes left and right
- No code reviews
- Mixing fucking local and cloud enviroment together
- No fucking testing
- Feature that were supposed to be implemented and are not working
- No configuration all the stuff are hard coded
- Full responsiblity for the whole stack
- Only one other guy with me
- And this fucking project has been delayed for a year
- MUCH FUCKING MORE WHERE THAT CAME FROM

Like what the fuck am I expected to do? I took the job thinking that people knew what the fuck they were doing and surprise surprise that was a fucking bust.

the problem is also I am the junior and these fucking people have more experience than me, what the fuck happened to over seeing people's work, PM doesnt give a shit, developers dont give a shit nobody gives a shit.

But when I got this surprise surprise now everyone is interested in finishing the project

BULLSHIT

Me passing time on the weekend

Random call from unknown number

Turns out it's the manager

M: hey , how is your weekend going ...

Me: nothing much ... Whatsup ?

M : yeah well , we wanted to push some minor adhoc fixes as some clients wanted it urgently

The Devops folks need developer support . Can you pitch in and monitor

Me : I'm not aware of what changes are going , i don't think i can provide support

M : don't worry it's minor changes , it's already tested in pre prod , you just need to be on call for 30 mins

Me : ugh okay .. guess 1 hr won't hurt

M: thanks 👍🏽

Me: *logs in

*Notices the last merged PR
+ 400 lines , implemented by junior dev and merged by manager

*Wait , how is this a *minor* release...

*Release got triggered already and the CI CD pipeline is in progress

*5 mins later

*Pipeline fails , devops sends email - test coverage below 50%

Manager immediately pitches in ...

M: hey , i see test coverage is down , can you increase it ?

Me: and how do u suppose I do that ?

M : well it's simple just write UTC for the missing lines ... Will it take time ?

Me : * ah shit here we go again

Yeah it will take time , there are around 400 lines , I am not aware of this component all together

Can you ask junior dev to pitch in and write the UTC for this

*Actually junior dev is out on a vacation with his girlfriend

M : well he's out for the weekend , but
as a senior dev , i expect you to have holistic understanding of the codebase and not give excuses ,
this is a priority fix which client are demanding we need this released ASAP

Me : * wait wat ?

---

I ended up being online for next 3 hours figuring out the code change and bumping up the UTC 🤦🏾

Someone gave me a web method that return a boolean.
The Boolean tells me if the operation went well.
True means everything went well
False means something went wrong

But
It throws exception when something went wrong.
Basically they implemented a Boolean system to check if everything is alright but I also have to add a try/catch if something is not right.

I was working for a startup that needed to update 300 machines that had just come from the factory. We had to open all 300 boxes and update them one at a time. I made a simple script that would run a folder full of shell scripts then keep track of what it ran so it would not run the same script twice. It made it so we could just plug the machines into the internet, they would query some server, download my program, and run it. It saved me from having to ssh into every machine and run commands. Well the head programmer guy saw what I did and implemented it as the main program that would update the entire machine. I didn't program anything into it to verify updates, the shell scripts did not return any indication of success or failure, and I made it in less than 3 hours. It was supposed to be a temporary program to be used for those 300 machines only, but ended up sticking around for 2 years.

Dev: Can you please tell me why you changed this?
Me: Because we need to handle permissions in the app. The quickest way of doing it, according to the docs, is [insert change log here]
Dev: But we can just check for the user's token.
Me: That's not exactly a permission, because...
Dev: I was only showing the information related to the user according to their token.
Me: I understand. But that means you're filtering data, not authorising users to access it. If a user is logged in, but changes query parameters, they can still access data they shouldn't be able to.
Dev: Whatevs.

Le me then proceeds to try to push my changes (that took the whole day to implement), gets a "you need to pull first" message from git, doesn't understand why, logs onto GitHub and realises dev has implemented their "permissions".

I was the one responsible for making those changes. Le dev was meant to be doing other things.

How do I even begin to explain?

Just got an email accusing me of not implementing a feature that is quite clearly implemented.

It's not my fault if your too stupid to #include my header file. Did you just expect the compiler to magically find the functions for you.

Also thanks for raising this with my team lead and his boss.

May you spend eternity in a cold ditch coding java script on a 386 with a 28k modem you disgusting fuck nugget.

SWIFT!!!!! I understand that you're a relatively new language so I forgave you for all of your wrong doings..BUT WHAT THE FINGER IS THIS SHIT YOU HAVE IMPLEMENTED IN YOUR STRING DATATYPE? WHY THE FUCK CAN'T YOU FORM A CHARACTER FROM AN EMPTY STRING? AND WHAT THE ACTUAL FUCK HAPPENED TO THE SUBSCRIPT OPERATOR? WHY NOT JUST ADOPT THE "\0" AS OTHER LANGUAGES? But NOOOOO...We're Apple we'll not adopt it..I WAS UNDER THE IMPRESSION THAT STUPIDITY AND LUCK OF INNOVATION RAN IN THE IPHONE TEAM BUT APPARENTLY ITS EVERYWHERE..Its annoying because the String datatype is one of the most common and basic data types so the last thing you expect is this shit..APPLE........SERIOUSLY AND SINCERELY FUCK OFF

Three days I'm not there, three bloody days and the 2nd sys admin has managed to:

Destroy the auto load balancing that I have scripted and implemented

Fuck up the backups to the cloud, and to a tape drive.

Overload a physical server (in pic, #1 and #2 are hypervisors). This is just one smaller site, I would hate to know what he has done elsewhere.

This is why I'm moving into dev.

Today i implemented something of such a complexity that the part of my brain i am in could not follow it.
(Really guys. I did not know what i was doing. I only knew i had to do it exact this way)

This feeling when you are in a tunnel and unstoppable. I even documented what i did.
Sadly i do not even understand my thoughts there xD
I wrote about three hours straight and then run a test. And the only mistake was a variable not filled as described. Used another one and it run smoothly as hell.

Today i will drink a beer on whatever part of me did this. Cheers

It works.

How I hate that sentence.

Whenever that sentence pops up, I wanna take a frying pan, make some bacon, eat the bacon and slam the still hot pan with grease through someone's face till the skull breaks.

Why has he so many anger issues, one might ask.

Usually the sentence "It works" means that after looking at "working thing" it works wrong in 95 % of all cases, but hey - for 5 % it at least does *something* right. Not everything, don't get ya hope up.

We had this fun topic happening again today and I'm still too angry to sleep.

Lucene analysis of texts in Elasticsearch.

Stopword list? Multiple word n-grams per line, duplicates, not lower cased, not properly encoded.

Tokenizers? Duh. Why should one put them in proper order.... Or more realistic: There is an order in tokenizers necessary *devs with shocked faces*.

Language specific details... UHM. Wait. Languages are different? There are edge cases in languages? *more shocked faces*.

Even more shocking that if an text processing pipeline is implemented horribly wrong, it delivers wrong results. *mind blown*.

But our unit tests (this goes out to @kiki) were working.

Yeah. You dumb nuggets who even an amoeba would be ashamed of, when you only do positive tests in unit tests with the most obvious working examples, then your unit tests are just useless waste of nibbles.

Some of the devs are really a fucking waste of genetic information, should have probably ended better in a sock.

If this sounds too harsh, they had 2 weeks.
In just 3 hours I found out that they can redo that with supervision.

-.-

I'm getting too old for that shit. Seriously.

Seriously does this master/slave bullshit actually affect everyone here?

From what I’ve seen it’s just a fucking idea / suggestion not a full blown change set being implemented.

Stop fucking over reacting to bubble wrap nonsense, if you want to call it a master/slave relationship then call it a fucking master/slave relationship and be done with it, if this really offends you or you believe political correctness is needed here, go call it something else, at the end of the day it’s still going to be the same thing, just called something else.

Last year, we had to do a big university project in randomly selected groups (5-6 students in every group).Three of the five guys were completely useless, I mean, both the other competent guy and me wrote around 20,000 lines of code each, the other ones wrote around 500 lines of code (combined).
After our first few meetings we quickly knew that we have to give them a small task which was so trivial that not even they can fuck it up. But we were wrong. Oh boy, so wrong.
They simply had to code the excel export of the data, which means they had to use two functions from a library and pass the correct data. But their solution was so bad, I lost faith in humanity and was fascinated by it at the same time.
For example, there was this simple class "Room", which had a few properties like size or number of seats and a few getter/setter etc. That was a core class and written by the other qualified guy. So how did the others fuck up the excel export? They somehow rewrote that class in German (although the other code was completely in English), implemented a function for each property that would write its value to a hardcoded cell in a hardcoded excel file.
And this was just the tip of the iceberg. Needlessly to say that I had to rewrite the whole export in the night before we had to present the project.

It says "There was no battery found."

This laptop was not connected to a power adapter, but Windows also said that there is no battery. Did I missed the update where Microsoft implemented magic wireless energy?

not sure if counts as a compliment, but the follwing exchange with my team lead programmer felt pretty good:

"... wait, where did you find this function you're using here?"

"i didn't, it was missing so i wrote it."

"but... oh, i didn't realize you're gonna need it, if i had, i'd have given you a different task... noooo, that's internal framework functionality, i write that stuff for you guys so that you can just use it, cause it's complicated... oh, god, no, where did you put, how did you imple... (right clicks, go to definiton)... oh, it's exactly where it's supposed to be... (skims the code)... and is written exactly as if i had written it.
(looks at me and smiles, then turns to the rest of the team), guys, that component i told you to wait with making because i first need to write that complicated utility function that you'll need to use? you can start working on it now, Midnight wrote that function for me. (turns back to me) Nice, quick learner. But next time, at least let me know first, yeah?"

(that was third day in a new job, corporate-sized system. the rest of the team had been working there on that system for the past 2 years.

(probably not a good form, kinda going over team lead's head, but tbh i didn't realize i'm not supposed to touch that code because "it's complicated", while doing my task i just realized i need a function similar to a family of already implemented ones, so i just followed their convention amd added it.)

tl;dr - best programming compliment is people being surprised/confused that i did something which they thought as a normal thing that they will have to do for me, because it's in their job description to be doing it for people on my position/with my job description)

Cons of not having proper documentation.

Wasted whole day reading code because I have to implement a feature. Turns out to that the feature is already implemented, just needed to be plugged.

15 years ago I had a job interview as technical leader. They asked me about the trendy framework in those days, Struts. I didn't know much to be honest. I actually started to study java the month before. I was 30 y.o. and I managed to sell myself well.

I got the job. I never saw Struts, the real job was to migrate a z/OS application written on PL/I for DB2 (all things where new to me, I programmed something in VB when I was younger, before studying a career in statistics). Anyway, somebody else already scaffolded Struts, I implemented some business logic here and there, and mostly tried to make sense of the monster-legacy.

Fast forward now.
Two months ago I was interviewed on the last version of Angular and AWS devops, kubernetes etc. I managed not to look completely idiot, but honestly, I never went beyond an Hello World in Angular, and kubernetes, well, I like the name.

I got the job as Technical Architect.

First project I'm assigned to: migrate a 15 years old Struts application to cloud.
Somebody has containerized everything.
Somebody will scaffold a dotNet application.

I'll watch. Maybe I'll write some nice powerpoint presentation. Maybe I'll fill in some business logic in some methods.

I wanted really to be a technical Architect and do things other modern people do.

I actually wanted to learn something.

Anyway.
For 160K$ a year is not bad, I wouldn't complain.

I really like how Opera Mini says it has an AdBlocker implemented, yet the app 'Contains Ads' according to Google. Guess it's not an effective blocker.

Tldr; my "this is not bug, its a feature" moment actually turned my bug into a feature.

Today we were presenting a project which has imposible deadline. I am developing this small project alone (which is probably good). I implemented core features first but I know project still have bugs and a lot of tech debts. Another friend started to presenting our demo and a wild bug appeared as expected. He was adding rows to a table. To add a new you gotta open new modal by clicking + button and fill the form. One of the fields had a bug. When you add row by clicking Ok button, the value of the field stayed there after you open modal again. So its basically a state problem in React. I forgot to clear previous state of modal. When they see that and my friend said "oh we got a bug there". Then I enabled my mic and said "thats not a bug, thats a feature. I didn't want to enter that field again and again when I adding multiple rows and made it persistent." and you know what? They liked the idea! They requested to add that bug to two more fields. I was just joking and my "this is not bug, its a feature" moment actually turned my bug into a feature. Instead of fixing it, I'm creating more of this bug. LOL!

Late one night I realize that Visual Studio has an update available.

> Might as well. Maybe they finally implemented that auto bug-fixer.

I download the update and it warns me that I must restart my computer. Fair enough, I was just about to shut down my computer anyways.

I turn off my computer for the night.

Boot up the next day, try to open Visual Studio.

It says to me: "No, I mean, you gotta RESTART. Not just re-start, or whatever shit you just did."

Ok. Restarted the machine.

Many people told me that all my face expressions look pretty the same. Whatever my mood (angry, happy, surprised) there is no much difference that appears in my face.

Well I didn't believe them until I tested a "Facial Emotion" program written on Python, and it gives me ~almost~ all the time that my facial expression is: Neutral.

Well, I think the algorithm is not well implemented 😐

Recent boot camp grad here with a solid portfolio...holy crap...this industry is so illogical...got a call from a recruiter whose job needs 3 years experience. I demonstrated I know every single one of the requirements, have implemented them, know pros and cons, etc. She says OK I'll run it by my manager and see because we can't fill the spot and it requires 3 years but you meet all the qualifications. I get an email the next day, and she says sorry, we actually need 5 years...fucking face palm...I'll apply again in 5 years because that job will still be open. Really sucks that the only thing holding me back from landing a job is experience, not knowledge. No employer wants to touch me with a 10 foot pole...how long will it take be to find a job...jesus christ.

sooooooooo for my current graduate class we were to use the MVC pattern to build an IOS application(they preferred it if we did an IOS application) or if you didn't have an Apple computer: an Android application.

The thing is, they specified to use Java, while in their lectures and demos they made a lot of points for other technologies, hybrid technologies, such as React Cordova, all that shit, they even mentioned React Native and more. But not one single mention of Kotlin. Last time I tried my hand at Android development was way before Kotlin, it was actually my first major development job: Mobile development, for which we used Obj C on the IOS part and well, Java on the Android part.

As some of you might now, I rarely have something bad to say about a tech stack(except for VBA which I despise, but I digress) and I love and use Java at work. But the Android API has always seem unnecessarily complex for my taste, because of that, when I was working as a mobile development I dreaded every single minute in which I had to code for Android, Google had a great way to make people despise Java through their Android API. I am not saying it is shit, I am not saying it is bad, I just-dont-like-it.

Kotlin, proves a superior choice in my humble opinion for Android development, and because the language is for retards, it was fairly easy for me to pick it up in about 2 hours. I was already redesigning some of my largest Spring applications using half the code and implemented about 80% of the application's functionality in less than 3 hours(login, fragment manipulation, permissions, bla bla) and by that time I started to wonder if the app built on Kotlin would be ok. And why not? If they specifically mentioned and demonstrated examples using Swift, then surely Kotlin would be fine no? Between Kotlin and Java it is easy to see that kotlin is more similar to Swift than Java. So I sent an email. Their response: "I am sorry, but we would much rather you stick with the official implementations for Android, which in this case is Java for the development of the application"

I was like 0.o wat? So I replied back sending links and documentation where Google touted Kotlin as the new and preferred way to develop Android applications, not as a second class citizen of the platform, but as THE preferred stack. Same response.

Eventually one of the instructors reflected long enough on it to say that it was fine if I developed the application in Kotlin, but they advised me that since they already had grading criteria for the Java program I had to redo it in Java. It did not took me long really, once I was finished with the Kotlin application I basically rewrote only a couple of things into Java.

The end result? I think that for Android I still greatly prefer Kotlin. Even though I am not the biggest fan of Kotlin for anything else, or as my preferred language in the JVM.

I just.......wish....they would have said something along the lines of: "Nah fam please rewrite that shit for Java since we don't have grading criterias in place for Kotlin, sorry bruh, 10/10 gg tho" instead of them getting into an email battle with me concerning Kotlin being or not being the language to use in Android. It made me feel that they effectively had no clue what they were talking about and as such not really capable of taking care of students on a graduate level program.

Made me feel dirty.

Hey, it's 2023.

If your component isn't written in TypeScript, I'm not using it :)

"TypeScript is overly complicated!!!" why, because it pointed out everything wrong in your JS code?

"TypeScript is not flexible!!!" why, because it makes you not rely on fragile "only possible in javascript" patterns?

"TypeScript isn't needed!!!" why, because you've never worked on a project with more than 100 lines of code where dependency management and clean code policies were implemented?

god just stop with the JavaScript purist BS, you aren't going to win this battle, and it's even worse because not only are you injuring everyone in the software community, you're injuring your own productivity and skillset

actually, you know what, fine. just use pure JS and HTML implementations. see you in 10 years when i'm retired and you are still running around in circles wondering why the world has left you behind

Hello devRant, this is going to be my first time posting on the site.

I work for a gaming community on the side, and today one of the managers asked me to implement a blacklist system into the chat and reactivate the previously existing one temporarily. This shouldn't have had any issues and should've been implemented within minutes. Once it was done and tested, I pushed it to the main server. This is the moment I found out the previous developer apparently decided it would be the best idea to use the internal function that verifies that the sender isn't blacklisted or using any blacklisted words as a logger for the server/panel, even though there is another internal function that does all the logging plus it's more detailed than the verification one he used. But the panel he designed to access and log all of this, always expects the response to be true, so if it returns false it would break the addon used to send details to the panel which would break the server. The only way to get around it is by removing the entire panel, but then they lose access to the details not logged to the server.

May not have explained this the best, but the way it is designed is just completely screwed up and just really needs a full redo, but the managers don't want to redo do it since apparently, this is the best way it can be done.

So the same guy who called Ninetails from Naruto a wolf is PM in this project with me

During scrum meeting:

PM: I read the project scope again and I realised there are scopes that we didn't get it. Each time I read the scope there's something new.

Me: *Sure, the scope is fucked with a long 8 feet dragon dildo to start with*

PM: Read the scope 5 times, cause we don't want to miss anything. If QA raises an issue regarding the modules which are in scope but you implemented it wrong then it won't be considered Change request and you have to do deliver it in time even work on weekends with no compensation.

Me: ...

PM: Now, go through the scope again today and we will hold a meeting after working hours (unpaid, but can be adjusted in monthly avg) and I will ask random questions.

Me: *tf*

PM: And anyone who won't be able to answer them will sit through the non-working hours and go through the scope again

Me: *YOU FUCKTARD, incompetence from your side or from business development team to create a simple understandable scope can't force us to sit through non-working hours.*

I already had an opinion about this guy from my previous rant, his improved a little in between but I guess not

anyone else have their own side projects where they follow no structure and pretty much make spaghetti code just to get it finished asap so you can make money off the system you are building? lol. not proud of the code i wrote today but damn did I get a lot of functionality implemented.

So, during my Java lessons we had a teacher who had a very special relationship with the language.
During the introduction he used to tell us that interfaces in Java are really poorly designed and that they would not reflect how an interface normally should be implemented. The possibility for a developer to add default methods to an interface or that a class could inherit from multiple interfaces was unacceptable to him.

Due to those reasons, he would hate on Java 8 and tell us to not use it and instead stay with Java 7 - dafuq!

So, I applied for a job. People tend *not* to answer my applications, probably because my resume very clearly states I implemented malloc in fasm, among other things.

I imagine them going like "Sir, this is a Wendy's", or rather "we're looking for a 10X rockstar AnalScript ZAZQUACH mongoose-deus puffery quarter-stack developer". Fair enough, I certainly don't fit that bill.

But this time I not only got an answer, the guy went like "I'm impressed". Is this... recognition? From a human? What?

Fellas, I cannot process this emotion. Being frank, it's not even about the job. But willfully going against the idiocy of the industry standard, and then seeing that utterly deranged move actually amounting to something -- no matter how small -- is quite uncanny.

And of fucking course, it's a Perl job. Figures. Great minds think alike.

When your client starts creating "bugs" for things that are not implemented yet... aaarghhh

Team estimated a huge feature with 60 days. Made a prototype in a day, implemented it in the project the next day. Code looks a lot cleaner than a previous similar solution.

Now it’s 90% done. Should have worked with 2 other people. Oh well, sorry not sorry for that teamwork.

Facebook 2FA:
Want to log in? Sure, authorize your login. Oh you've authorized it? Nah you can't get in. Log in again.
2FA, excellent technology, except when it's implemented by "move fast and break things" Facebook.

Facebook Marketplace:
Want to buy $listing? Sure, you can send a message to the seller to ask for details. Oh, you want to send them a message? Nah sorry, you can't send messages to this person. You'll have to go to their profile, send them a message there and do it not with our le fancy instant messages but by manually typing it in. Because you know, reasons. Message approvals or something like that probably. Because why on Earth would Facebook support its own ecosystem?!

Move fast and break things. And breaking things those certified enganeers at Facebook sure do. Fucking pieces of shit.

A few days ago someone posted a pic of an ESP8266 microcontroller, so it reminded me that I have one of those lying around with a board with a screen I built during summer, so I thought, why not making a devrant reader, and so here it is:

For now it can only read rants, posting is coming soon, the software keyboard is already implemented

We call it the thing (Accrocchio in italian)

Spent 6 hours implementing a feature because my senior didn't want to use a 3rd party plug-in.

After said 6 hours, went to look at the plugin's source code to get some inspiration with a problem I was having.

Guess fucking what? Plug-in was implemented exactly as I had done it to start with. Even better, actually, since it fixed some native bugs I couldn't find a way around.

Went back to my senior, showed him both sources and argued again in favour of the plug-in.

Senior: "Meh, I'm not sure. Don't really like to keep adding plugins"
Me: "Why? Do they cause performance hits? Increase memory usage?"
S: "No, not all. But I don't like plugins"

/flip

We ended up using the plug-in, but I "wasted" a whole day doing something we scrapped. Guess I learned some interesting things about encryption on Android, at least...

Spent a lot of time designing a proper HTTP (dare I even say RESTful) API for our - what is until now a closed system, using a little-known/badly-supported message-over-websocket protocol to do RPC-style communications - supposedly enterprise-grade product.

I make the API spec go through several rounds of review with the rest of the dev team and customers/partners alike. After a few iterations, everybody agrees that the spec will meet the necessary requirements.

I start implementing according to spec. Because this is the first time we're actually building proper HTTP handling into the product, but we of course have to make it work at least somewhat with the RPC-style codebase, it's mostly foundational work. But still, I manage to get some initial endpoints fully implemented and working as per the spec we agreed. The first PR is created, reviews are positive, the direction is clear and what's there already works.

At this point in time, I leave on my honeymoon for two weeks. Naturally, I assume that the remaining endpoints will be completed following the outlines/example of the endpoints which I built. When I come back, the team mentions that the implementation is completed and I believe all is well.

The feature is deployed selectively to some alpha customers to start validation testing before the big rollout. It's been like that for a good month, until a few days ago when I get a question related to a PoC integration which they can't seem to get to work.

I start investigating and notice that the API hasn't been implemented according to the previously agreed upon spec at all. Not only did the team manage to implement the missing functionality in strange and some even broken ways, they also managed to refactor my previously working endpoints into being non-compliant.

Now, I'm a flexible guy. It's not because something isn't done exactly as I've imagined it that it's automatically bad. However, I know from experience that designing a good/clear/future-proof API is a tricky exercise. I've put a lot of time and effort into deliberate design decisions that made up the spec that we all reviewed repeatedly and agreed upon. The current implementation might also be fine, but I now have to go over each endpoint again and reason about whether the implementation still fulfills the requirements (both soft and hard) that we set out to meet.

I'm met with resistance, pushback and disbelief from product management and dev co-workers alike when I raise the concern that the API might actually not be production-ready (while I'm frantically rewriting my integration tests and figuring out how the actual implementation works in comparison to what was spec'ed).

Oh, and did I mention that product management wants to release this by end-of-week?!

[wordpress trigger warning]

Had an idiotic colleague who re-implemented the insert image function as a shortcode. A “senior php developer”. No, I’m not kidding.

Him: “But this way we can set a class”
Me: “As you can with the standard mode”
Him “No you can’t”
Me: *shows*
Him (smiling): “well why don’t you remove my stuff then?”

It's 5 AM and I don't want to shit on anybody's party but trust me when I say most of you here complaining about legacy code don't know the meaning of the word.

As someone who maintained a PHP4 codebase with an average file length of 3000+ lines for almost 4 years, I feel you, I feel your pain and your helplessness. But I've seen it all and I've done it all and unless you've witnessed your IDE struggle to highlight the syntax, unless you had to make regular changes in a test-less SVN's working copy that **is** the production and unless you are the reason that working copy exists because you've had enough of `new_2_old_final_newest.php` naming scheme, you do not know legacy. If you still don't believe me bare in mind I said "is" as in: "this system is still in production".

But also bare hope. Because as much grief as it cost me and countless before me, today of all days, without a warning, it got green lit for userbase migration to a newer platform. And if this 20 years of generous custom features and per client implemented services can be shut down even though it brings more profit than all the other products combined, so can happen to any of your projects. 🙏

Unfortunately, I do mean *any*.

Just saw this in a production app. There's a reason no other language implemented VB's OnErrorResumeNext, BECAUSE IT'S A F***ING TERRIBLE IDEA.

Catch (exception e)
{
//not really an issue
Continue;
}

This incident is from my college days.....

I saw one of my friend was arguing with his project partner. He was pretending to know everything in programming better than his partner.

Just for fun, I asked him to implement single linked list by using arrays/pointers (I gave him 20 mins and told him to do in any programming language he is familiar with). He was not able to do, so I suggested him to use Google and see if he can find something which can help him with implementation....

Within 10 min he came with a solution which was working fine. So I asked how does he implemented, and what does the methods do.... As expected, he was blank and I got to know he copied entire solution from Stackoverflow.....

A thought came in my mind:
Just by knowing copy/paste won't make you a programmer....... <\>

I'll be honest, I've never understood why people say that numbers generated by a computer are pseudorandom and not random.
I know a lot of algorithms for number generation, and I implemented mine, based on time of invokation expressed in nanoseconds, taking digits, manipulating and transforming them. Then I analyzed the probability distribution and it's absolutely flat. So, if you know the Touring test, we can use a modified version of it. If I give you a sequence of random numbers generated by a computer and I give you a sequence of random numbers invented by a person, and you can't notice the difference, so the test is passed.
What's wrong on it?

Fuck you Intel.
Fucking admit that you're Hardware has a problem!

"Intel and other technology companies have been made aware of new security research describing software analysis methods that, when used for malicious purposes, have the potential to improperly gather sensitive data from computing devices that are operating as designed. Intel believes these exploits do not have the potential to corrupt, modify or delete data"

With Meltdown one process can fucking read everything that is in memory. Every password and every other sensible bit. Of course you can't change sensible data directly. You have to use the sensible data you gathered... Big fucking difference you dumb shits.

Meltown occurs because of hardware implemented speculative execution.
The solution is to fucking separate kernel- and user-adress space.
And you're saying that your hardware works how it should.
Shame on you.

I'm not saying that I don't tolerate mistakes like this. Shit happens.
But not having the balls to admit that it is because of the hardware makes me fucking angry.

There are clients who always suggest an idea then after they suggest they will say "...again don't do this yet, its not a big deal blah blah blah"
Then the other day they will ask if their idea is already implemented.

🤦🏻‍♂️

ME: Here's an endpoint to get all the textual info about the entity. And this one fine endpoint is to fetch entity's files

FrontEnd: This is no good. I need all entity info in a single JSON

ME: but files could be quite heavy, are you sure you wan...

FE: Yes, Just give me all the info in a single JSON

ME: okay... I hope you know what you're doing..

ME: <implemented as requested>

ME: <opens a webpage with 2 files attached>
Browser: <takes 30 seconds to open a page and downloads 30MB of data in the JSON>

ME: As mentioned before, your approach is a performance killer

FE: No worries, we'll fix that in the next version. First let's see if anyone will be using this feature at all - maybe it's not even worth working on

ME: <thinking> I know I would NOT be using an app if it takes over half a minute to open up a chat channel. FFS I wouldn't even be using Slack if it took 30 seconds to open some other conversation, because for some reason it wanted to fetch all the uploaded files along with all the messages each time a channel is clicked on.....

ME: <thinking> this project is doomed :(

Good question, what wasn't bad about 2020?

As far as good things go.. well, COVID-19 actually. Back in February the lockdown began in Belgium, and while many people got bored out of their minds, I actually became a lot more productive. So many projects started back then, and I got a lot better at programming because of it. Now I can confidently write most bash stuff without ever looking anything up. And the code is maintainable, on account of putting everything into functions. You can literally navigate the code just by looking at it. On older code I always had issues with that.

I'm very glad that essential travel even back then wasn't really restricted. Because my bank is retarded about online banking, I have to go to the bank every so often to check my balance. At the time I tended to do that late in the evening, when nobody else was outside and I had the entire town to myself. That was one of the travels considered essential. So I kept doing it and made that my biweekly walk. I really enjoyed that. Gets your mind off things.

Bad things would be the utter stupidity that the general public had shown me during that pandemic. Burning down 5G antennas and not even getting the right ones, toilet paper, 5G death beams in street lamps?! They even sent death threats to telco workers over sensationalist bullshit from what IIRC was just a random Twitch streamer. Those people should just fucking kill themselves, choke yourselves in that pile of toilet paper you got yourself and then called yourself financially challenged. You braindead fucking retards!

Another dev-related thing is the normalization of SJW terminology. Now even "blind playthrough" gets your ass banned on Twitch. I saw a tweet about a Twitch employee (I think) proudly saying that they implemented it. Most upvoted comment on it was from a blind person, asking why they did this and not made the Twitch app more friendly to use for blind users. They too thought this was bullshit. Yet it still got added in, and more and more people are starting to think that "this is fine". Hell even that "this is necessary".

What annoys me the most is that this mostly comes from the US, where around that time they laid their knee on George Floyd, and didn't fix their legal system at all. As a European it baffles me since we have many immigrants here (the Drumpf even called Belgium a hellhole over it) and we just don't give a shit about whether or not they are "truly Belgian". We just let them live their daily lives like everyone else. Imagine just not giving a shit. Imagine not bothering them, not with racism, not with reverse racism, not with anything. Just let them do their thing and that's it. Yet despite Belgium being one of the most inclusive countries in the fucking world, I still got called a racist many times for asking.. why did you implement this? Why this, and not tackling the problem at its actual and pretty fucking obvious core?

So all in all I can only hope that 2021 will get a little bit better. But that's the same thing I said in 2019, and it didn't quite come true.

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

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

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

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

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

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

My very first rant here was about the mess of ticket submission and ticket tracking applications we use, and about how we were moving to a single unified system some day.

Well, that day is today. And, predictably, it went horribly wrong.

So the way it's supposed to work is people login to the portal, search for what they want to request, then fill in details and submit. It creates a request ticket assigned to the appropriate team. (The old way involved a bunch of nonsense that you can see in my first rant).

The thing is, I found out about this today, when I got a company-wide email saying the new system was live as of this morning. None of us knew it would happen today. Not that I could've foreseen any issues just by getting the announcement early, but still, usually people find out about these things beforehand.

So, ecstatic to finally be rid of the old ticket tracking system, I log into the new system and look for our request form, which is, of course, not there. I check the old system and see that they combined every single "general request" into a single request where you pick which team the request goes to.

So I finally find the right request, pick the right department from the drop-down, and see that the request looks much better than it did on the old system. Out of curiosity, I look at the list of people who are part of that department.

I am not on the list.

My ENTIRE TEAM is not on the list.

Because they migrated the team data to the new system a year ago, when the issue tracking/reporting portion of it went live. My current team was hired approximately six months after that and apparently updating the team data in the new system isn't part of our Onboarding process yet.

So... Bright side is I guess I will have a lot of free time soon since nobody can submit new project work to my team?

tl;dr: they took a great software product and implemented it so poorly that our team can't use it.

Well not bad for my first try eh? I implemented a std::vector-like container and it's about 4 times as fast as std::vector

A few years ago I was working in a startup where the designer was given way too much decisional power (he was friends with the owner).

He had a tendency to keep editing parts of the design during the development phases, so when we had to work on a new big section of the application, before starting the tront-end development, I asked him to confirm that the mockups were final.

He confirmed the design was final and was not going to change.

10 days later, of couse, he sent a new, completely different, set of mockups. The startup owner expected the new design to be implemented without moving the deadline.

(I left that startup shortly after. The issues with the designer were just the tip of the iceberg.
The owner tried to keep a payment hostage to "force" me to sign a new 1 year contract. He backtracked when he thought I was recording the call. I got my payment and left.)

I'm so tired.
Got enough sleep but tired nevertheless every day.

Situation in the company isn't helping, would really like to get a review as I'm really close to a 'final' version for productive use, none given.
Didn't think far enough and didn't include various OO-things when starting to program this application, so I had to rewrite lots of it. It certainly got better by the time but as it's a grown structure I'd feel happier if someone other than me had seen and cursed the code.
Coworker that has most experience in C# only once implemented something with multiple threads, couldn't help me there.
Could not test the code yet because the hardware was inaccessible and is now potentially broken.
I really like working independently, nevertheless I feel a little bit lost at sea - I can deal with that, but it's exhausting.
Also, trying to get an answer from the colleague who should act as my supervisor whether or not I can work remotely during a CS related course in the semester break for > 2 weeks now. Course admission is the mid of January so I'd like to have an answer this year so I can repeat the basics I'll need if necessary.
Also, Midterm is coming.

It's a lot of little things piling up right now I wouldn't mind if there were only 1-2 of them.
I'm just so damn tired.
I'll go to sleep now.

(In happy news: my internet connection is working pretty decent now, technician that fucked it up apologized and said that he probably needs glasses, he misread the connection number. :D)

Seriously? Microsoft does not support ed25519 SSH keys in neither Azure DevOps nor the actual Azure Virtual Machines? Like seriously? No there has to be a joke. There just ain't no way
It has been in OpenSSH since 2013.
2013.
We're in 2023, if you've forgotten.
10 years ago, OpenSSH implemented this standard.

Did you know what they tell you when you enter your valid Ed25519 SSH key into their system?
Did you know they tell you that "Your SSH key is invalid"?
WHAT DO YOU MEAN INVALID???!?! IT WORKS EVERYWHERE ELSE JUST FINE!!! YOU'RE THE ONE THAT HAS NO FUCKING BRAINS!!!

Composure.

I am calm, I am calm.

I have always. Been. CALM!

There is no one more calm than me....

I guess RSA it is then.
A second SSH key, just for Microsoft.

daily.
me: i looked into the customer dev's project and even though it's C#, i can use it as a source of inspiration for my own C++ library.
PM: okay, maybe we can even still use it, so that you use a C# dll with your C++ code.
me: ...
other colleague: that's a bad idea. it can already be a challenge to use unmanaged c++ in dotnet, but the other way round it's even more difficult. C# and C++ are languages that behave quite differently and it will be hard to implement a correctly working interface.
PM: okay. well... then please analyze this project's complexity in terms of LOC and create a class diagram, so we get an idea of how complex it is.
me: sure.
PM: hmm... maybe we should split this topic. since dev x will also rely on your library, analyze this project together with him, each of you look at another part of the classes.
me: that's.... i think that's a bad idea. implementing this functionality in this library is my job, not of dev X. he won't be involved in implementing any of the funcionalities and for him, it shouldn't matter how this works.
PM: yeah, but since we are prototyping, maybe we should just violate the "separation of concerns" rule.
me (internally): (ノಠ益ಠ)ノ彡┻━┻

in the end i could convince him to do it my way, but for fuck's sake... when was the last time he actually succesfully implemented something? 🤦‍♀️

Im gonna turn this topic on its head a little and mention the MOST NECESSARY feature that was never implemented in one of my projects.
It was an iOS client for a medical records system. Since it contained actual confidential medical information, some patient records could be “restricted”. Thos meant if you tried to open them you would be prompted for a reason, and this would be audited.
We already had 2 different iOS apps with this feature in place matching the web app. But for some reason with the 3rd app they just decided not to bother. I discovered that it was because the PO in charge of that project didnt consider it important enough for the demo. So we have one app where you can just bypass the whole auditing process and open restricted patient records freely.

Fucking people, why the hell are you reading into things instead of asking for clarification if something is unclear?

So much time, sweat and tears wasted on miscommunication.

When I said, "there might be a problem in the way component X method Y was implemented", i didnt mean go refactor the entire code of the component. Why waste 2 days of work on unnecessary refactor that nobody wanted and breaks changes + the bug is not fully fixed 😤

Go to the vacation.

Return back to see all those useless features that should not be part of the MVP, that I have previously rejected multiple times, poorly implemented...

Now we have to maintain this shit, that nobody even uses in real life...

Fucking imaginary use cases...

You know that you made it as dev when you realize that your creation has ability to effect your life also the life of others

It came to me much earlier in life ( college final semester)
F: Hey there is this girl that i am trying to talk but she never replies me on Facebook i waste to much time looking for her online status , i wish if i can say hi as soon as she comes online
HF: (first reaction) leave her alone man , ( dev reaction) hmm fb probably be using jabber protocol like xmpp I could make xmpp client and sync online status. If status changes drop a notification also the asmack lib provides a way to send msg to user in your chat room sooo we good !!

At the time i was handling 3 android app , implemented this and called it FacebookStalker , you can select who you wanna stalk and what msg you wanna send them as soon as they come online

Google obviously didn’t liked it
for a long time i judged myself that How can i can make this creepy app
Later I realized that it was not the app i was suspended because i used a DRM marked image as icon

Google never tells you the actual reason why your app is suspended so you cannot fix it.

I learned to be mindfull of what i code cause it started having real impact. Loosing dev account was like loosing everything at that point. i had nothing else

I wish my boss would stop revoking my permissions. He's always saying how these slew of things need to be accomplished, yet, everytime I go to do them I'm at a wall because, despite having permissions for a very long time he decided to revoke them entirely.

It's not like I can't be trusted with them, it's been over 2 years with them, so why the sudden revoke?

I finally sent some snot mail to him informing him I'm unable to complete my tasks without the permissions granted to me (I'm a sysadmin, sec guy, boss is vp of tech), and instead of him granting them yet again he's going to run around and try to hack around the permission requirement so he can avoid giving me them.

Seriously? This is stupid. I was the one who wrote the security design and implementation document, and put all that work in. Now I'm being locked out of the system I designed, built and implemented?

Well, time to look for a new job. If you're a manager, please don't revoke your employees permissions without notice, at random, and try to hack around well-documented security policies. It won't end well!

Created 'GET STARTED' section in our application in English. It will guide new user to Highlight some App features.

End User started Posting screenshot of it in our feedbacks service : What this is?

Implemented 'GET STARTED' in local languages.

End user started posting screenshot of Language Drop Down, what this is?

Implemented 'GET STARTED' on Location based Language.

End User : I am here in Banglore seeing it in Different Language, my other Partners in Hyderabad are seeing it in different language. What this is?

Removed 'GET STARTED'.

End User : It was a nice feature. Why you removed it? What this is?

May be i over reacted but i am not bringing it back.

Noticed a rant on here about transactions not redirecting the user back to the previously visited page, on certain sites. Just implemented the functionality to my shitty little project and I currently feel better than the big players.

How bad it feels when it work in a place where Agile and DevOps are mostly abused buzzwords.

Forced doing "scrum" with:
- half of the team providing endless daily reports instead of focusing on the 3 questions
- a scrum master that is barely reachable
- a product owner that would not even make a decision
- a sponsor that pushes us to go faster regardless of current technical debt (it's important to look good to other sponsors!)
- doing all possible scrum ceremonies with no value added
- not even estimating stories
- not even having accurate description in stories. Most of the time not even a description.
- half of the team not understanding agile and DevOps at all

Feels so good (not). Am I the one in that boat?? ⁉️

What's the point of doing scrum if implemented that badly?? 😠

Client: Hey new iOS 11 is coming soon, is out app compatible?
Me: Not sure, let me shift the development to new Xcode 9 and test it out.
Client: So, how was it?
Me: pretty straight forward. all seems fine a couple of bugs.

But then when trying to fold a big function to make things easier to read, you discover that Xcode 9 beta 1,2,3 & 4 DOESN'T FUCKING SUPPORT THAT YET. How on earth is this not yet implemented?

Customer requested the implementation of a "Master PIN" Code for accessing their appliances, to be used by field technicians when the users forgot their PIN.
Actually they could also read or reset it via USB using the config utility, but then again it's much more convenient not having to carry a laptop all the time...

Our only contact person at that company - the guy we got all the requirements from, let's call him Mr. L - wouldn't talk only positive about the company and managers, but we never worried as the project was making good progress.

In the final phase of the project, Mr. L was often hard to reach, always seemed to be busy even when we just needed a prototype approved to start production.
He always claimed to be waiting for approval from his supervisors and engineers, still discussing minor things with them.

When he left the company about three months later, it turned out he was pretty much the only person knowing about the details of the project, and his successor would start asking us very basic questions about the appliance,
wondering why we had implemented certain things the way they were.
(Well, how about we implemented everything just as requested by a former co-worker of yours?!)

Somewhere in the preliminary specs previously exchanged with Mr. L, there is even a hint of a "Master PIN", but the value is never specified anywhere on paper.

Today, we are not sure if anyone except for him even knew about it.
Maybe we should ask them whether they are now selling a product that has a 4-digit backdoor PIN nobody at the company is aware of?

Obviously, it is the birth year of Mr. L.

A beautiful gem ticket from a manager today:

Title: "Check Stripe "Snippet APK" that might help for integration into the app to track pricing easily."

Alright, it's very clear this particular individual has no idea what they are talking about, but, I'll give them the benefit of the doubt and read the ticket description!

Description: "I think stripe offers some sort of snippet that can be implemented into the app similar to FB pixel. (I could be wrong here..) let’s briefly check this, if it’s of value for our A/B-Tests → e.g. if it makes your life easier = good otherwise it’s not important."

...

I might as well replace the management team with GPT-3 at this point.

Or even just a simple Markov chain; that'd probably be more accurate if you want to match the ticket quality more exactly of this ABSOLUTE PILE OF HORSESHIT WASTE OF TIME I GET FED EVERY SINGLE FUCKING DAY.

🤡

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

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

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

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

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

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

.. :D

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

My first freelance project - happened to be with the worst client. They didnt wanna pay more than $500 and also had no clue what they want, so each time i present something they request additional features or changing the ones implemented. In the end i kept the half downpayment for my time and bailed without deploying or anything. I introduced them to another freelancer to take the project and never went near them again.

To clarify, it was not my first project/ just my first time dealing with clients for projects instead of doing them at work. Ever since then i have a strict no dealing with clients directly policy.

I used to do some freelance work for a nonprofit. I’d do some website stuff and gallery sitting.

My friend was the gallery director. When she left, I decided to stop freelancing there and I dropped off the keys with the new director. I told them they could contact me later if they have questions about some things I implemented on the website. The new director thinks I’m a random freelancer and starts to BADMOUTH MY FRIEND, the former director.

Over a year later, the gallery assistant emails me asking about SSL warnings and cc’s the new director. WTF.

1) Those warnings were happening long before I left and long before I even started. 2) I am not your website support. I only invited contact for things I worked on. 3) The assistant already contacted Squarespace and Go Daddy for help and they gave her instructions.

I told her I didn’t set up their website and it sounds like she has the resources to resolve this on her own and she should contact Squarespace and Go Daddy if she needs more help. After all, you pay those companies for their services support and my time isn’t free.

Keep it simple, but at the same time try to build it so that any known or unknown future change can be easily implemented. Do not block your future.

so... 9 years ago we had this super awesome codebase. 1 file, complete logic COPIED to be used in ui and service/daemon. I scrolled to the middle of the file and there was no source. it was out of bounds of my monitor to the right because of nested ifs. ok... what the fuck!! the worst part: I had to implement a new FEATURE into this mess. 2 days. I said it would not work as expected because the feature was not thought through. but project said let's gooooo! ok there I was, a junior with an impossible to implement feature and a codebase from hell. I've implemented something, all night long. next day it was the problem of the consultants. they called me, I told them why it's impossible that this would ever work, they understood and talked to the customer. he accepted the solution. WTF?! anyway, in those days I thought about quitting developing software as my daily job....

Almost burnout story? What about right now...

Customer was really positive about the new site we are creating for them then, out of the blue panic, they complain about features (calculations) which aren't implemented yet (they didn't provide any information for the calculation until 1 week ago.) And they complain that the site does not has any content

THAT IS RIGHT YOU DUMB FUCKS...
I can't magically create content for YOUR site...

A: "Mate, do the translations"

B: "Fine, but you guys implemented the translation service so repetitively..."

A: "No, this is not repetitive, that's how we need to do it"

*sigh*

PS: Whenever I call the "trans" method, I think of transgender, don't ask why

I beg your pardon that I did not implemented the mind-reader API and my app doesn't know if a discount is expired when you DIDN'T FUCKING SET AN EXPIRATION DATE YOU ARSEBADGER!!

Priceless advice to all. Never agree to work on a project where graphic designers are overseeing it. You will be installing a scripty handwritten font the week before go live, changing out images but the ecommerce portion has not yet been implemented much less tested. I thought I would be implementing a typical Shopify site but no it is "story telling" they say. Oh yeah go live is 4 days away.

IMHO technical dept is kind of like smoking cigarettes for some decades.

You were told that shit will hit the fan but you do not take proper action. And one day you'll realize that you fucked up (or not, also seen that).

Worked for a company in IT, where we maintained an ERP which was "in progress" for over a decade. The basic implementation was done by people with zero technical understanding. To clarify: not self coded. Software was bought. We are talking about integrating the system.

Therefore, the foundation was like a wet noodle. When I joined that company, I told them that they need to address that. I told them that things will get slower and slower and that shit will hit the fan if no proper actions taken.
Even made a list with flaws I found. With potential risk and actions to take, that could then be measured.

At that time, five people worked in said department (including me).

People did not want to listen. "Would be too expensive to rewrite stuff".

Nothing has changed about the wet noodle, but I tried to fix as many things in a working system as I could. Felt like heart surgery, because changes got implemented and "tested" in prod. No version control, no documentation, everyone implemented things like they felt (no guidelines for consistency).
A lot of small fuckups that summed up over the years.

I left the company after two years because I had the chance to land a job as a dev.

Been around two years now since I left. Now 9 people work in that department with around the same efficiency as us 5 people back then.

The new employees struggle to be productive, because things are just implemented poorly and not maintainable anymore.

Had some dialogs with them some time ago. Everything I told them would happen, actually happened. What a suprise :-|
I will not go into too much detail about all the shit that's going on there, as it would be just too much (and my morning coffe is almost finished).

I think that we all know the difference between "not beautiful, but does the job" and "oh, that will backfire - badly". And I wish that my communication skills increase so that people start listening in future.

So there's that project with my coworker. We splitt up the classes, 10 to be implemented by him, 10 by me.

Fast Forward to 4 weeks before deploy.
Coworker: Your stuff logs a lot of stuff. It's not very clear and a liiittle to verbouse. 5 entries per second? Too much!
Me: Okay, you're right. Let me fix that.

2 Days later I look at his logs at runtime. He logs EVRY SQL statement and their results! In a batch that processes a 10'000 of customers!
He points out: That's useful stuff and it's not that much. It's needed for debuging.

My face: 😦

So when code is badly written, more corner cases are unnecessarily introduced. And it’s sometimes tricky to find the corner cases and probably messy to fix the corner cases.
And so the code grows in size as a result. And when these fixes to the corner cases are not well done, they introduce more corner cases.
So what results is a large collection of corner cases. Only corner cases remain when this goes on for a while.
Because of this, every new feature can be effectively translated to a collection of corner cases to be implemented.
As corners grow, triangles become circles and tetrahedrons become spheres.

I live in such a sphere.

#5

Of course the previous dumbass dev could not use the findOrFail() method, because he didn't used any models.
But he just implemented his custom get404() method.

😓🔨

i was hired to join a team of old devs (40+) in an unnamed European country "yay goodbye 3rd world it's time to enjoy the quality of life" assist with enhancing already existing software and creating new solutions.
prior to my arrival most things were slow and super buggy, looking at the code base it shouldn't be a surprise, amateur hour everyone, logic implemented that is not needed, comment driven development, last time code review was done back in 1996. lots of anti patterns.
i swear there is a for loop that does nothing but it loops through a 100+ elements list, trunk based development with tfs since git is "not really needed"
test projects are not there.
>enter me an educated fool, with genuine passion for the craft and somehow a decent amount of knowledge.
>spent the last year fixing stuff educating people on principles and qualities.
> countless hours of training and explaining. team is showing cooperation, a new requirement comes in to develop with react.
> tear my ass creating reusable shit and self explanatory code with proper naming etc using git with feature branching, monday is first deployment day.
> today a colleague was working on an item submit a pull request and self approve it
> look at the code..... WTF the dumb fuck copied and pasted the whole code from different kendo components but somehow managed to refractor the name to test component, commented out all the code that he didn't use did the api call directly from the component, has 2 useeffects that depends on the a fucking text box changes for no reason, no redux implementation, the acceptance criteria is not achieved, and it doesn't work it just look right.
> first world country shit cannot scold, cannot complain, lead by example.
>asked him why you did this, the response was yeah probably i shouldn't have done that, i really didn't understand anything in the training but didn't want to waste time!!!!
> rest of the team created a different styled disaster with different flavors they don't even name their shit the same way.

fellow developers I'm stuck in a spaceship with a bunch of imposters, seriously i never cried in my entire life now I'm teary and on the verge of a break down.
talk with management "improving needs time" and offers me to join a yoga session to release the stress as if reaching nirvana would deliver shit on monday.
i really don't know what do is this a rant, is this a cry for help, I'm not sure, any advice is welcomed.

I explained last week in great detail to a new team member of a dev team (yeah hire or fire part 2) why it is an extremely bad idea to do proactive error handling somewhere down in the stack...

Example
Controller -> Business/Application Logic -> Infrastructure Layer

(shortened)

Now in the infrastructure layer we have a cache that caches an http rest call to another service.

One should not implement retry or some other proactive error handling down in the cache / infra stack, instead propagate the error to the upper layer(s) like application / business logic.
Let them decide what's the course of action, so ...
1) no error is swallowed
2) no unintended side effects like latency spikes / hickups due to retries or similar techniques happens
3) one can actually understand what the services do - behaviour should either be configured explicitly or passed down as a programmed choice from the upper layer... Not randomly implemented in some services.

The explanation was long and I thought ... Well let's call the recruit like the Gremlin he is... Gizmo got the message.

Today Gizmo presented a new solution.

The solution was to log and swallow all exceptions and just return null everywhere.

Yay... Gizmo. You won the Oscar for bad choices TM.

Thx for not asking whether that brain fart made any sense and wasting 5 days with implementing the worst of it all.

So, I am a couple of more months in working in my new role. Learning the trade and boy do people have a lot of fucking things to say! It’s incredible the AMOUNT OF BULLSHIT these people get away with…

Background, I’ve been a software consultant for a number of companies working in different sectors in different development roles for +16 years. I built everything from RS232, iOS to BI. Shifted to permanent developer for large global corporation where I got promoted to clown.

Anyway, anyhow.

FUCK, these FUCKING people!!!

Meeting after meeting after endless pointless discussions and even more pointless fucking powerpoint presentation which if you stack them on top of each other will reach the FUCKING top floor where there are even more morons. FUCK!

There is absolutely NO cohesion, there is NO plan, short-term or long-term, no vision that can be practically implemented. There are different organizations of equal power and the result is a FUCKING MAZE.

But people travel the FUCKING GLOBE. You know, THE FUCKING PLANET EARTH, for pointless workshops and alignments (plural). FUCK!

And it’s getting worse. We’ve got consultants hiring consultants now whose job is to hire consultants. True story! And it’s not that high up the org chart either!

It’s a beast! A retarded beast.

We are NOT helping.

I got to get out of this fucking corporation. So, I am starting to design my exit strategy. The master plan.

Used a starter to scaffold a new project. Have never used that starter before but it has more than 1400 starts on Github.

Two days after.... so far so good. The created project structure used some tools I haven't used before, some are good, others are not so good, but anyway I am towards the first release of my codes. I have done countless 'npm run build', 'npm run test', 'npm run fix', etc., but.... my fault, I haven't committed once since starting the project, thinking I would commit when the next function is implemented, next test case passed.... after all, what could go wrong anyway?

Finally, one last test case passed, I think I will commit and run 'npm publish'.... but wait, had a glimpse of the scripts section in package.json, there's a command named 'all'. An voice came out of nowhere was talking to my subconscious mind, "all.... build, lint, prettier, test..... yeah you should run all... it's another build script, the worst you can get is just some harmless error messages.....", and my fingers typed 'npm run all'...

Time stopped for a few seconds, file structure in project explorer was shifting, files & folders were disappearing & appearing, what's happening... and I looked at the 'all' script closely for the first time....

WHAT THE HELL, WHO SHOULD PUT 'git reset --hard' IN A BUILD SCRIPT WITHOUT ANY PROMPT????!!!!!!!

MY PLAN WAS TO COMMIT AND GO TO SLEEP, IT'S 1AM NOW!!! WHERE CAN I RECOVER THE LOST FILES????

Me: The dev agency didn’t follow best practices. They only implemented front end validation on the form. The form submits to a public endpoint, so bots don’t have to go through our site to submit the form. That’s why our database is still filled with $1 donation transactions. I honestly recommend telling this to the dev agency and request that you not be charged for the extra work needed to do this right.

Manager: They charge $95/hr and they’re billing for 8 hours already.

[Aside: The agency’s task was to implement a $10 minimum on the form, do some text changes, and deploy.]

Me: I would expect work to be done according to accepted best practices. It’s really a half done job.

Manager: But they were very helpful when we had that payment processing emergency. They stayed late to help us. We shouldn’t push this in case we need their help again. Can you do the backend validation? [We are in US and agency is in Lithuania.]

Me: 🤬😩😑🤐[To myself: This wouldn’t have happened if the fundraising team hadn’t panicked and would only wait until I came back from my one day of PTO.]

I was working with a stable installation of an elaborated platform. Some plugins were installed. After upgrading the installation by 2 patch level the customer registration was not working anymore.

In these two patch level a method in an interface got an additional optional parameter which had a major impact on the behaviour the implemented method. A plugin decorated the implementation without knowing about the new parameter. Therefore when calling the method the decorating class did not pass the new parameter in to the decorated implementation and the fallback value was given instead.

The caller expected the method to do something and did not branch into an alternative way but the default value disables the expected behaviour. Eventually nothing happened.

Breaking changes in patch levels woop di fucking do.

Me during a presentation of a website for university project. It's a simple project for our university where there is internships offer for our field, stack : php, js, css (bootstrap), and the presentation was on my computer, so on localhost.
In that projet i have implemented a back office to manage all the offers, basic CRUD functionality, and as lazy as I am, for delete confirmation i used a simple javascript alert for that.
Me during the presentation :"so here is the back-office to manage users and internships offer, and for deleting one offer you just have to click on this trash icon *click*".
Ze professor : "hold on hold on, why it's showing 'localhost' "
Me : "it's javascript alert"
Prof : "but why 'localhost' "
Me : "oh, because i'm running the website on my computer as a server"
Prof : "but why localhost, it's not professional"
Me : *god please "it's javascript alert rendered by the browser, we can't do anything about it, and for a simple application it's sufficient"
Prof : "but why it's bigger than the message, and if we host that, do we steal have that localhost"
Me to end that : "I'm sorry i made a mistake on that".
Fortunately i had a good mark on that project.
It's my first story here, and sorry for ze bad English ^^

We were documenting a feature which has system wide affect. We’ll be delivering it to customer on Monday.

So we’ve asked the colleague who worked on it about how it works and asked few follow up questions that arise during the documenting. All were good.

Comes Friday when I had a question as some things didn’t add up and I checked the source. To my surprise the very core operation colleague explained us works in exact opposite way. I kid you not in %50 percent of the documentation we ramble about why it was implemented this way since it is faster/safer best practices bla bla.

Moreover we’ve already had some exchange with the customer and we informed(misinformed) them about this core operation...

Also changing the behavior will reduce the overall speed as it will cause extra branchings. Other option is to rewrite the documentation and inform(re-convince) the customer. If it was me I wouldn’t trust us anymore but we’ll see.

I really don’t know what to say about this fucker why would you say something if you’re not sure of it or why the fuck you didn’t confirm in the last 3 weeks....

Anyway we have a meeting on Monday morning to discuss how to proceed, that’s gonna be fun!

Describing a friend's project to a friend:
"And then theirs a tinder like element, for filtering potential dates, but that's not implemented yet."
"Why doesn't he just copy tinder?"
"Er... wat?"
"You know, just copy their code and put it in his app."
"You don't... you can't... I mean you can decompile... but that's not useful because... it just doesn't work that way. For a million reasons. I don't know where to begin."

You know what's fun? When your client insists you use an agile process with a delivery at the end of each sprint, then proceeds to bitch at each release at the features that weren't implemented yet. The thing isn't even slated to be done until 4Q 2018 and is on schedule/early. Glad I am not on that team . . . yet.

I used to be a Java fanboy.

After seeing the modern things one can do with other languages I am just disappointed, that Java is so old-fashioned.
Some would say "BUT IT HAS LAMBDAS".
Good, that we have lambdas. We don't have optional parameters or objects (like in JS's {} or PHP's stdClass).
JVM may have many advantages, but I think, that Java is slowly dying although it is kept alive by some companies, still using Java in prod.
I think, that Kotlin is, what Java should have been.

I hope, that my wishes will be implemented in Java 10. If not, Java is considered as dead.

What the fuck this fucking shit of an app supposedly went through five rounds of QA and I broke it in 5 minutes? Holy fucking shit How this is the main point of your job. You shitty shits take forever getting this PR to me and now it’s buggier than a haunted house on Halloween?

After this is after wanting to cuss Apple for making me update the os then then xcode then iTunes just to recognize the goddamn development phone. It’s an app built off Cordova it works for like 14 versions of iOS just run the bugger you over priced aluminum chassis dildo riding fruit Fuckers.

Now back to the goddamn cluster fuck I just got delivered. What the goddamn fuck. This level of bullshittery I have not seen before. And apparently Cordova is only partly de-sandboxed? I don’t know for sure because I don’t have time to test it because I’m running the entire technological stack of this company on a junior dev salary!

When you tell me it goes though all this QA and you spend 2 weeks on just QA tickets for fucks sake the first operation I do, the most common fucking operation on the app, the shit we have been building around all this fucking time, should not fucking error out. For fucks sake at least try to get the main fucking thing working. I recognize you did a lot of work and implemented a number of features but what the fuck good are they if I can’t even run them for one fucking time.

So, this incident happened with me around 2 years ago. I was pentesting one of my client's web application. They were new into the Financial Tech Industry, and wanted me to pentest their website as per couple of standards mentioned by them.

One of the most hilarious bug that I found was at the login page, when a user tries logging into an account and forgets the password, a Captcha image is shown where the user needs to prove that he is indeed a human and not a robot, which was fair enough to be implemented at the login screen.

But, here's the catch. When I checked the "view source" option of the web page, I saw that the alt attribute of the Captcha image file had the contents of the Captcha. Making it easy for an attacker to easily bruteforce the shit outta the login page.

You don't need hackers to hack you when your internal dev team itself is self destructive.

Go to bed tired. Wake up tired. Get up tired.
A month ago I was excited doing my work, I even was planning a huge change on one of our projects, detailed everything and passed it over to other folks to get funding. Now I seriously doubt I could pull it off. When I start reading a line of code I forget how it started before I reach the \n.
There was this thing I was asked to implement... A nifty one, I already could see the implementation. As I came to it I got stuck. Like when your body gets "stuck" when you get scared to death - you know what you have to do (i.e. RUN), you know how, but for some reason you just can't... Couldn't come up with anything. The other dev had to take it over and implemented it all in like 4 hours. Just like that. And it took me another 4 hours to understand how and why it worked when I know it should not take me that long as I used to write similar algorithms myself for fucks sake! I know I could have written it myself... but I couldn't..

I'm seriously worried.. Is this the end of my carreer as a dev? Am I broken somehow? I have some vacation days saved but I doubt it would be enough... Don't know if changing workplaces would work as well. I've always wanted to leave 9/5 and start working on my own project full time but now I am not sure I could pull it off either.. wtf is happening.. wtf... wtf..

Once I implemented a giant ASCII skull for logging a fatal error in the company's app. Let's just say my feature did not get to production.

Ok, so we have the Spotify Agile Model now (tribes, squads, chapters, etc). I have seen it implemented in a few large companies, and they seem to be doing ok.

It's just... doesn't anyone worry about the product that came out of this great way of working?

Spotify is great as a service, but it has to have one of the worst usability/success ratios of any modern mobile / web app. You can almost feel the various squads doing their own thing, not thinking about the whole experience.

Doesn't the product count when considering using someone's way of working? Is the Spotify Agile Model the project management equivalent of Twitter's Bootstrap?

My ++s are not implemented.

This remote agency that we use to help us build our mobile app is taking the piss out of us. They always have stupid questions, more stupid questions and on top of that at least they don’t work fast. So a task that should take a day it takes them a week and when they deliver it’s not exactly what we’re asking. Despite the fact that they’ve already asked me tons of questions they went ahead and implemented something I haven’t asked for because they thought it’s better. Well guess what read your fucking requirement documents that I spent 2 days writing. It’s all there bullet point by bullet point including the way it should work with examples and justification plus a flow charts to make it super fucking clear. It must be their business model to fuck around, stay on the project for as long as possible and ask for more money. They can’t be that stupid.

Been hacking frontend for a while, know most of the perks and tricks of css and html, have implemented countless of projects with angularjs, have even created jquery plugins and gulp packages, have won hackatons in UX design.... Still, a SFO company turned me down for a front end dev position cause I could not find the K most frequent words in an array in O(n) time complexity...

[CMS Of Doom™]
Ah, yes, their built-in bullshit newsletter module just sent the n-th user n emails. Wonderful considering n=368.

The culprit? Better don't ask...
OK, anyway: So the mailer is running as a CRONjob, but nah, not as a console script call but by a public HTTP GET URL call, fucking obviously (it's the CMS Of Doom for a reason).
So these fucking imbeciles "implemented" an ob_start() callback where HTML links are - for whatever fucking reason - modified by some regex (obviously everybody knows parsing HTML by Regex is trivial). In this case the link was somehow modified to recall the mailer Cronjob...
This must have upset the pngoing mailing process thus spamming mails. Whyyyy

And I've thought I've seen it all after 6 months in this legacy hell...
This is why you don't run a company consisting of only beginners in PHP (in cluding their "CEO")!

I hate those persons...

*sigh*

Don't do this.

Person does it.

Don't do it. We are currently overworked and this _must_ be a project every team agrees on. Otherwise it will end exactly like it is currently - a big mess that every team implemented differently.

2 hours later....

Person books time for said project.

Other team lead: Stop working on it. This makes no sense.

Person: yeah... But I needed to clean it up anyways, so I just started cause why not.

--

Me and the other team lead had a 5 min discussion about it shortly after...

Wasn't the first time said person has gone solo rogue *sigh*

Despite that this is driving me (and the other team lead) nuts...

WHY THE FRIGGING FUCK DOES HE ALWAYS DO IT WHEN WE ARE SO FUCKING OVERWORKED....

Really. Every fucking time this mother tugging bullshit kindergarten play.

I think it's the first time that I said: I don't care - I'll just trash his work when we start on the project as a team in 2 months (Yeah... That's realistic. 2 months minimum...).

The universe really has it's way to make me angry.

I hope he stops tomorrow, we really cannot deal with emotional bullshit at the moment.

*gooozfraba*

How can such fuckwads exist....

Okay so i graduated last year and got a job working for a place that sadly disappoints me in their web development practices. This place uses a dead technology(my opinion)called Cold Fusion by Adobe. They do not use any form of version control like Git and their sites are very shitty and the design and development is implemented very poorly honestly. It honestly makes me sad that i feel like im smarter than my department vp. That being said i do not feel challenged here and am looking to collaborate in some open source projects via Github preferably.I dont consider myself an expert in this field but i would say im about intermediate level in web development. Im pretty comfortable with HTML,CSS/SASS,PHP,JS/JQuery, and im pretty comfortable in the PHP framework Laravel. So if anyone is interested in collaborating or starting something up, id be so down for it. :)

Most pissed off I've ever been at work when was I attending some development meeting about the "slow progress we were making", in which the boss (same one giving us shit for being slow) came up with several new good ideas that he wanted implemented ASAP. Same thing he'd been doing all year; fucking up our plans and adding a metric shitton of feature creep. I tried to give realistic estimates for how long it would take to implement, and casually mentioned that working on this would also push back the other stuff on our plate, but he snapped at me and accused me of being a "negative influence" and "sabotaging the project", and went on in a long rant about how we didn't take the work seriously enough and that we didn't put in enough effort.

I was a hair's breadth away from flying over the table and strangling him with his keyboard cable, and the only thing that kept me in check was the tiny amount of steam I vented by snapping the pen I was holding in two. We'd been working overtime every day for months to try to meet his insane demands and accomodate him by doing all the changes and additions he wanted done, and I found his tirade - mainly targeted at me - highly unfair.

Somehow I managed to exercise restraint, and I'm not sure if he even realized what happened.

This is actually a question about the devRant app.

I’ve noticed this a few times. When I click a rant repeatedly (say x times), from the front page or from the notifications pane, multiple layers of that rant open up. And I have to hit the back button x amount of times to go back to where I initially was (again, front page or notification pane).

Now, I understand an app capturing multiple user inputs on the same object but shouldn’t it also account for this by only considering those taps as one input, especially if the object is lagging and hadn’t been loaded? Why is devRant implemented this way?

I would consider it undesirable to have Gmail open the same email in multiple layers when you click the same email repeatedly. So, is devRant’s a feature or a bug?

I’m not a web (app) developer. I’d just like some knowledge on how user input might be captured and why repeated inputs aren’t screened out?

If anyone could page the two awesome doods who work on devRant, that would be awesome! I hope I didn’t just wrongly assume their genders.

TL;DR; do your best all you like, strive to be the #1 if you want to, but do not expect to be appreciated for walking an extra mile of excellence. You can get burned for that.

They say verbalising it makes it less painful. So I guess I'll try to do just that. Because it still hurts, even though it happened many years ago.

I was about to finish college. As usual, the last year we have to prepare a project and demonstrate it at the end of the year. I worked. I worked hard. Many sleepless nights, many nerves burned. I was making an android app - StudentBuddy. It was supposed to alleviate students' organizational problems: finding the right building (city plans, maps, bus schedules and options/suggestions), the right auditorium (I used pictures of building evac plans with classes indexed on them; drawing the red line as the path to go to find the right room), having the schedule in-app, notifications, push-notifications (e.g. teacher posts "will be 15 minutes late" or "15:30 moved to aud. 326"), homework, etc. Looots of info, loooots of features. Definitely lots of time spent and heaps of new info learned along the way.

The architecture was simple. It was a server-side REST webapp and an Android app as a client. Plenty of entities, as the system had to cover a broad spectrum of features. Consequently, I had to spin up a large number of webmethods, implement them, write clients for them and keep them in-sync. Eventually, I decided to build an annotation processor that generates webmethods and clients automatically - I just had to write a template and define what I want generated. That worked PERFECTLY.

In the end, I spun up and implemented hundreds of webmethods. Most of them were used in the Android app (client) - to access and upsert entities, transition states, etc. Some of them I left as TBD for the future - for when the app gets the ADMIN module created. I still used those webmethods to populate the DB.

The day came when I had to demonstrate my creation. As always, there was a commission: some high-level folks from the college, some guests from businesses.

My turn to speak. Everything went great, as reversed. I present the problem, demonstrate the app, demonstrate the notifications, plans, etc. Then I describe at high level what the implementation is like and future development plans. They ask me questions - I answer them all.

I was sure I was going to get a 10 - the highest score. This was by far the most advanced project of all presented that day!

Other people do their demos. I wait to the end patiently to hear the results. Commission leaves the room. 10 minutes later someone comes in and calls my name. She walks me to the room where the judgement is made. Uh-oh, what could've possibly gone wrong...?

The leader is reading through my project's docs and I don't like the look on his face. He opens the last 7 pages where all the webmethods are listed, points them to me and asks:
LEAD: What is this??? Are all of these implemented? Are they all being used in the app?
ME: Yes, I have implemented all of them. Most of them are used in the app, others are there for future development - for when the ADMIN module is created
LEAD: But why are there so many of them? You can't possibly need them all!
ME: The scope of the application is huge. There are lots of entities, and more than half of the methods are but extended CRUD calls
LEAD: But there are so many of them! And you say you are not using them in your app
ME: Yes, I was using them manually to perform admin tasks, like creating all the entities with all the relations in order to populate the DB (FTR: it was perfectly OK to not have the app completed 100%. We were encouraged to build an MVP and have plans for future development)
LEAD: <shakes his head in disapproval>
LEAD: Okay, That will be all. you can return to the auditorium

In the end, I was not given the highest score, while some other, less advanced projects, were. I was so upset and confused I could not force myself to ask WHY.

I still carry this sore with me and it still hurts to remember. Also, I have learned a painful life lesson: do your best all you like, strive to be the #1 if you want to, but do not expect to be appreciated for walking an extra mile of excellence. You can get burned for that.

It's a really interesting discussion, when your boss tells you that it's a perfectly fine idea to directly use a Firebase DB from an Angular web app by storing the Admin Auth Token in a variable in JS.
Thank the spaghetti monster, I was able to argue against it and use the already partially implemented RESTful API with the already used auth.
He basically wanted to save time and omit extra login routes.

It's OK to save time and not implement $randomFeatures.
BUT DON'T FUCKING TRY TO SAVE TIME ON SECURITY!

If it wasn't for me, this web app would turn into a bigger gaping (security) asshole than Sasha Grey's...

You can connect to Docker containers directly via IP in Linux, but not on Mac/Windows (no implementation for the docker0 bridged network adapter).

You can map ports locally, but if you have the same service running, it needs different ports. Furthermore if you run your tests in a container on Jenkins, and you let it launch other containers, it has to connect via IP address because it can't get access to exposed host ports. Also you can't run concurrent tests if you expose host ports.

My boss wanted me to change the tests so it maps the host port and changes from connecting to the IP to localhost if a certain environment variable was present. That's a horrible idea. Tests should be tests and not run differently on different environments. There's no point in having tests otherwise!

Finally found a solution where someone made a container that routed traffic to docker containers via a set of tun adapters and openvpn. It's kinda sad Docker hasn't implemented this natively for Mac/Windows yet.

Asked to implement a feature in a mobile app that wasn't actually supported by the backend. Feature had 3 possible values in the backend, only 1 and 2 were properly implemented. Below was the backend teams solution to support the third option.

- If the key is missing in API response A, means the user is not allowed access this feature.
- If the key is present in API response A, and missing from API response B, that means it hasn't been set.
- If both are the same value, user has that value.
- It will never be the case that both return option 3.
- If both are different values, one of them being option 3, display option 3.

this ... monstrosity, is in production to this very day.

Currently working on a web platform for a building management company for the last 6 months.

Setup web server, database and developed the whole using laravel and vue.

They are in the testing phase now, so I implemented IPSec so that they can only access it from their office.

Thing is, they don’t have a static IP, so when they had to switch over to a backup connection yesterday, I had to add their new IP in my whitelist.

Today I get and email from their manager, saying that after a discussion he had with his assistant, the web app is not in the “cloud”!!! He got that because I had to “do something” to restore access to it yesterday and because “there isn’t an icon you can double-click” on each employees’ desktop!!!

Don’t even know how to respond to that!!!

Generally devs who are too arrogant to accept help or constructive criticism. There’s this data visualisation library that missed a specific feature that psychologists use quite frequently, so I added it myself and opened a PR. The maintainer closed it because people should use whatever he’d already implemented. It’s like not giving someone the option to listen to disco because rock music is better. Yeah, cool story bro. Now all my visualisation projects depend on my fork instead. Same with the now abandoned Material Design Library devs. They didn’t have a drop down with free input, so I opened a PR with my solution. Closed as it was out of scope, simply because Google didn’t specifically include that in the Material specs, only an input and a drop down separately which my solution matched. I also opened a PR for an obviously missing feature (being able to validate forms via JS), closed as this behaviour wasn’t in the Material specs either. No wonder MDL died before it was ever finished.

Rust ahahaah hhaahah ahah

the trait bound `std::result::Result<std::string::String, std::io::Error>: std::convert::AsRef<[u8]>` is not satisfied
the trait `std::convert::AsRef<[u8]>` is not implemented for `std::result::Result<std::string::String, std::io::Error>`

This is to anyone that has a MacBook Pro that has a Touch Bar.

When you’ve programmed on the MacBook have you ever implemented the Touch Bar’s accessibility into the application? And is it easier or more out of the way to try to implement it into the application. Also could non OSX related languages be used or can only Swift, Objective-C, etc

Only curiousity, my MacBook Air doesn’t have one, and I’m gonna eventually upgrade to a pro and I’ve heard good things about the Touch Bar but not about using it in applications.

I have never encountered a codebase so horrendous. The styles are so fucking bad.

Give me a codebase with a poorly implemented programming langauge, fine.

Give me a codebase with styles that have been copy/pasted off Stackoverflow a million times until something works, not fucking fine.

I don't understand the hype among the non technical people about Blockchain! Why the fuck they want to implement everything in Blockchain? Don't they know that it is not for every single application and mostly used for some trustless applications?
Now one of our clients wants his restaurant website to be implemented in Blockchain!

I came home about 1am and saw a bug in a small (unpaid...) project that had to do with timezones (see some earlier rants). Fixed it, got to bed.
A few days later I realized that a feature I implemented before was gone. Going through the git log I found out it was me in that night who removed it, by accident I suppose.
Not the end of the world but I was quite intrigued by my own drunk ability to remove a feature that had nothing to to with what I was doing and not even noticing it.

Looks like I got dislike-banned as well... eventhough I only used it where appropriate.
I understand that our almighty gods dfox and trogus implemented this to fight bots and mischievous downvote cunts, but why not inform the user affected by it?
I fucking hate these silent bans, just like Twatter and YouTwat do it... you feel like you posted something but in reality it disappears and you're not even aware of it.

Man, nowadays a lot of people behave like bots thus I can't blame The Algorithm™...

how to php, an infographic by Bind (that me)

0) assert your goal, in this example let it be sending an email from the server
1) search for implemented methods
2) all you can find is either outdated or not helping at all
3) think of solution in any other language (eg c# or node)
4) implement 3)
5) iterate until you have something that works but you have no idea why
6) after 1 week, realize that there is a built in method, but its called userData_registration_sEnder0(adress, header, egg, pinNumbe_r, message)
7) cry

- Implemented oauth1 - no body hashing
- URL contains credentials in plain text
- Used Azure API management feature as a proxy of the our API, however the documentation was on the our API, thus exposing the API URL with no management to developers.
- easy resource DDoSing because each trial user got a DB, the registration process did not have bot checks. You could literally freeze the db instance by spamming registration requests.

Why things are fucking hard when you're not too good and not too bad at work. I'm like normal dev just throw things at me give me any task any framework I will learn it, I will solve production issues, I will help my co-workers to get their shit done even my JIRA is clean but it feels like I'm going nowhere. I'm like an average guy who knows many things other than normal guys or devs (by considering I'm junior and the people who are working with me).

I'm feeling like I'm in a fucking loop, where every day is same.
Is there anything I can do? which will make me feel little better?
I think every guy on earth have some innovative ideas even I have some(of course some of them are implemented already even they are kinda same, even some ideas are totally new, some are not possible, some requires much knowledge of certain field). But by just having an awesome idea doesn't change anything.

Maybe I'm not trying hard, there are several other reasons which are coming in my way but of course, I shouldn't tell any reasons.

I love when a project puts a dependency on infrastructure that has not been implemented internally and have no idea if it will work. *sarcastic voice*

Mine: not listening to early warning sings that shit won't work. As a result we implemented the wrong technology and had to roll back after a month in production. Lost some customers data, though we had backups, so it was just a delta of a day or so. Still, not pretty, had a rough night writing scripts at 3am to check data validity after.

I will throw in another one from a colleague of mine. He was running some database migrations and ended up pointing the DB migration tool to production by accident. Oops. That one required a restore as well, if I remember correctly.

Needed texts to call-duty with the gist of the incident. Implemented, works.

PM wants to also ring the phone, cause text may not wake them up.

Me, telling him, that his tools don’t allow me to call him. However, I said, I could send the text as a fax msg, which would end up “ringing” mr call-duties phone, and then fax-Morse-beep the msg to him.

PM was ok w/ that.

So I've been hired as a senior software developer with all the tags included (mentoring, innovating, pushing forward changes) for a company that is trying to move away from waterfall development (yup, it's 2019 and this exists) to a more iterative workflow.
I was initially hired and sent out to do some "field work" abroad for 3 months and then worked "remotely" from the local office with our field partners.
During all this time it seemed that my ideas go through smoothly, there was a lot of chatter about how things are moving forward, how new projects, innovations and new methodologies are implemented.
And yet, after my "remote" work has finished and I have to do things locally more, all of the skeletons fell out. It's just talk, nothing seems to be changing at all and yet any attempts to talk with the brass is like hitting a brick wall.
Not only that, I've been handed a 12 year old project with no possibility to refactor, no technical documentation, very few comments and in a terrible style.
The atmosphere in the company is odd as hell. People are either not very initiative, nor they seem to really care about all of the "changes" that "should be happening".
It almost feels that I've arrived in a company that still lives in 2007 more or less.
Should I quit, or perhaps it's a little "too soon" (have spent 7 months in the place already)? What I don't want is to get in the same train again (work for a company for 8 - 12 months, feel burned out because of the divergence between actual things done and "plans" and then change the job).

So I joined a pretty big organization, and am working here for like the last 4 months. Barely wrote any code, mostly I have been documenting stuff, and testing stuff of other devs.
So I had a doubt regarding a functionality, like what I asked a senior dev was, Where exactly is this logic implemented in the codebase so that I can refer it. He was like, you are supposed to know it since you have worked on a testing ticket of it. And if I ask the manager such questions, he would be pissed off. My point of view is that yes, I might have seen that logic, and it might have been explained it to me once, but at that point of time, I did not knew about which functionality it was being used for. am I in the wrong here? Am I not paying enough attention to the code base given It's my 4th month here?

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.

Today I've implemented two custom annotation and two validators for those annotations (Java). It's a huge nested object so it's not as easy as I thought to begin with. That pretty much the only thing I've been doing today, and I feel like I've added absolutely no value to the company and feels a bit ashamed not to have done it faster when I look back at how simple it actually was. Makes me wanna choke myself...

PHP code that didn't use sanitize, but manually checked if strings contained ' or ". Not even in a function, but manually implemented whenever the person writing that burning dumpsterfire thought it was a good idea to check for that.

Code also didn't report, it just exited without error code. Users would just get a white screen if that spaghetti code "security" system got tripped.

New day. New legacy project that needs triage.

The project has existed since before 2000 so it all "works" and has no known business logic bugs. It does however have performance issues which sure I can have a look. It can actually be quite fun and rewarding to optimize performance.

This is a titanic dotnet framework leviathan consisting of over 12,000 cs files using razorpages, entity framework, and... nhibernate? I have my gripes with both EF and NH but they are both fine if used correctly, like any other tool. I've never seen them used together however.

As It Turns Out™, NH was implemented first and at a time when NH did not support async operations. It made sense if you look it up and it's meant to delegate commands via a separate layer, but different story.

Then for... reasons... EF came in and gradually took over.

Because of the way this is all set up, everything will faceplant if you try doing anything async, even if it has nothing to do with calling the db. Any attempt in making this work leads you down a slippery slope of having to rewrite the entire thing, which is out of the question in terms of their budget and expectations.

Sometimes it's a detriment when it works in spite of its issues.

I implemented the equivalent of “?.” In typescript with a function callled safeRetrieve(descend into the field only if the object is not null).

We could not update typescript, so I just created this function and it made me used to use ‘keyof T’ as a parameter type… I still feel very satisfied after I use this approach with anything because it really feels like using typescript correctly!

i started a project a couple months ago and i used ORM for the queries, cause it's already implemented. thing is, this project came directly from hell and the math is stupid af. it requires subqueries in subqueries and the data that was provided is trash. I'm giving up on the ORM, it's not scalable.

I've been creating my Typescript/C# projects using SOLID principles. Whenever someone randomly joins me in my projects at work, i feel they need a lot of help. Specially since they know programming, but are not familiar with SOLID.

Like ohhh ok you created a base class for that, or ohhh that method already exists in the base class sorry i've implemented it again, or ohhhh ok you already implemented this method in that class.

The more classes i create the more complicated it becomes, sometimes for me too!
I feel I have to write a documentation for the code I write just to keep up with the different, but code changes/augments so writing a doc is really time consuming.

However if i didnt create base classes or interfaces it would be less complicated to browse through method definitions.

I am happy with the code like that though, but in some specific times it's a pain in the ass.
Comments?

Why developer of c# (Anders Hejlsberg) when developing (TypeScript) not implemented method overloading and interfaces' methods implementation with same names.

Allright, so now I have to extend a brand new application, released to LIVE just weeks ago by devs at out client's company. This application is advertised as very well structured, easy to work on, µservices-based masterpiece.

Well either I lack a loooot of xp to understand the "µservices", "easy to work on" and "well structured" parts in this app or I'm really underpaid to deal with all of this...

- part of business logic is implemented in controllers. Good luck reusing it w/o bringing up all the mappings...
- magic numbers every-fucking-where... I tried adding some constants to make it at least a tiny bit more configurable... I was yelled at by the lead dev of the app for this later.
- crud-only subservices (wrapped by facade-like services, but still.. CRUD (sub)services? Then what's a repository for...?). As a result devs didn't have a place where they could write business logic. So business logic is now in: controllers (also responsible for mapping), helpers (also application layer; used by controllers; using services).
- no transactions wrapping several actions, like removing item from CURRENT table first and then recreating it in HISTORY table. No rollback/recovery mechanism in service layers if things go South.
- no clean-code. One can easily find lines (streams) 400+ cols long.
- no encapsulation. Object fields are accessed directly
- Controllers, once get result from Services (i.e. Facade), must have a tree of: if (result instanceof SomeService.SomeSubservice1.Item1) {...} else if (result instanceof SomeService.SomeSubservice2.Item4) {...} etc. to build a proper DTO. IMO this is not a way to make abstraction - application should NOT know services' internals.
- µservices use different tables (hats off for this one!) but their records must have the same IDs. E.g. if I order a burger and coke - there are 2 order items in my order #442. When I make a payment I create an invoice which must have an id #442. And I'm talking about data layer, not service or application (dto)! Shouldn't µservices be loosely coupled and be able to serve independently...? What happens if I reuse InvoiceµService in some other app?

What are your thoughts?

So I've finally implemented face detection in my discord bot.

@Wisecrack regarding the openCV training, I'm still taking positive and negative samples, so it'll be another while.

Also, why is post @ing not a thing

In my project to process CSV file it needs to be transformed into XML file. Basically 100 MB CSV is turned into 3GB XML. They can be deleted afterward but it is not implemented and no one cares. Our storage gains around 1-2 TB data each month. Right now we have ~200 TB of XML in our s3
I think I can add Big Data to my CV *sarcasm*

All of the basic features of the rewrite have been successfully implemented! Ranting, commenting and even different types of posts have been implemented.

In 1 fucking month. Fuck, if that’s not impressive I don’t know what would be honestly.

Now - time for notifications.

Let's see what's on the menu today:

* Web Application Catastrophe Special *

Includes, but not limited to:
- Orphaned server processes in the configuration management cluster
- Microservice back-end architecture with no API documentation
- Poorly implemented cache microservice with no documentation
- Stale data causing everything to be shown as down in production, despite everything running fine

Cost: 1 developer's sanity

Trying to make a deadline, waiting for more info from an analist so I can implement the science stuff correctly

Today I receive the email with the info I need. Email is cc'ed to the client. And it starts with complaining about me not having implemented the science stuff. The info I need is attached in this email. Arghgh, how am I supposed to do that if I don't have the information I need.

Apart from that she was testing in the production environment. How do you work with people like this.

But hey, I just got my devRant stickers ;)

A: [technology] really sucks. For example, it does this thing where [shitty thing].

B: So just because [shitty thing], you throw out the entire [technology]?

No you dimwit. It's because of all the other things that led up to this point. This new bullshit is just being tossed on top of the mountain of other bullshit.

I'm not going to list off all 5000 reason why Cobol-interpreter-using-C-preprocessor is absolute garbage when "it's cobol implemented in the C preprocessor" is what I'm ranting about *now*.

Pedantic twats.

I've done it! I've implemented a new feature. I call it, wheal. its just like the wheel you know and love, in every way, shape, and form. But now, you can take comfort in knowing the state of the art has surely progressed, every time you go to reference, "wheal". This has the added benefit that others who may already be familiar with wheels, will have no trouble at all coming to terms with wheals. Just please, do not make reference to wheels, or your software will not compile. And also be sure to annotate all instances of wheals *wheals are just like wheels!* until all devs have been on-boarded.

I just implemented the cookie popup you wanted me to make. And now you give me a call that your tracking code doesn't appear in the source code?

Oh, but you don't see the cookie popup? You saw it right? So you've already set your cookie permissions, probably not to accept tracking cookies. We can check by... what's that?

If I can make the tracking code appear anyway?

...

Yeah, sure, no problem, change will be live in five minutes.

AHHAHAHAHHAHAHAH Not only did my StarSpace got "hacked" i would say abused , but I had my password in clear text so did he GOT MY DevRant account now aswell!!

I just implemented encrypted passwords yesterday but not fully since im still testing ...

( hacked by @tallasianman )

:(