Yes Linus Torvalds is an asshole and the world is better because of it.

In short Linus's acid takes on code quality over developer fee fee's might be one of the things that has made the Linux kernel and the GNU/Linux project such a long lasting open source success and in my opinion the risk of him falling for all this "let's be nice and non offensive" bs trend may impact negatively on code quality.

Being an asshole has it's downsides and it's not always the best response, I'll give you that, but personally I think most of us who are viewed as assholes are seen like that because we put quality over convenience, facts before feelings and dedication over mediocrity; it is not because we hate you, it's because we measure ourselves with the same stick.

It depends on one's character, but when you've been toughened up because of bullying(I don't doubt many devs have been since being a nerd has never been hip) or life in general, you learn to stop whining & pick yourself up and you expect everyone to be competitive and competent as you are and it gets frustrating to manage people who don't fulfill your expectations.

Pros: You get shit done and you do it well.
Cons: People won't like you and you don't tolerate failure (much less mediocrity).

Yes Linus is an asshole, my coach was an asshole, some of my best teacher's have been assholes, I had friends who were assholes, heck I'm an asshole!

But I thank them because they made me better than I was, just as people have thanked me for being the right amount of asshole.

A warm thank you and fuck you Linus, keep being the asshole we need.

PhD applications in computer science are so fucking frustrating. I have responded to so many invasive questions so far. The only private information universities haven't asked yet, is my bra size. The only contact they haven't asked for yet, is my kindergarten teacher (And her bra size, coincidentally). The only document about a potential project I haven't given to them yet, is my freaking dissertation. None of these have anything to do with my research potential, btw. There's nothing asked of me about my research aspiration and how I actually undertake a research project.

And then suddenly it occured to me: people in Academic administration are not smart. I'm actually explaining my potential to a pretty dumb bunch (Excluding those in research, none of whom will bother with these stupid documents).

... The world seems to revolve around stupid people. Fuck.

Boy do I hate office politics...

A client asked our company to fix perf issues on their product. Our coleagues had been picked for the job [being led by another 3rd-party, as per client's request]. Aaand they dropped the ball. The deadline is in 2 weeks, nothing is working.

Mgmt engaged us to put out the fire, but strictly at the scope the other guys were working in.

On the first day of testing we've revealed an elephant-sized perf issue that's as easy to fix as brainlessly changing 4 values in config. And that elephant is masking all the other perf issues.

We got a firm NO for config changes as that is out of the defined scope. And we're asked to continue testing.

I mean, the elephant is THAT huge that any further testing is moot - all other bottlenecks are hidden behind it. And just changing those 4 values would reduce the resources required by a magnitude of ~10.

But that's out of scope...

Client is desperate, lost and honestly asking us, pros in the field, for help.. We know how to help.. It takes 10 seconds to apply the fix..

But our mgmt forbids us to step out of the scope :/

as a result we have to pretend to be dummies hardly knowing what to do and hide the truth from the customer they so desperately want.

This is frustrating. And wrong. And imo unprofessional

IMO, salary range must be mentioned with job descriptions!

A candidate investing so much time & efforts to pass through the entire interview process only to know that their compensation will be lesser than what they're currently paid is very frustrating.

Remember the super duper company I applied for? (Last rant)

Well, I did their coding challenge. And after many years I had to do a metric crapton of C++. It's not a fun language. It's frustrating how human-unfriendly it is, and maybe one reason why I low-key like it.

Anyways, here's hoping that I didn't fuck up too much.

On a side note, I realized tensorflow actually has a cpp api. I think I'm gonna work with that in my next mental breakdown. 🧐

New HOE came. He “streamlined” the processes and “standardised” the policies. And in turn.. fucked up the whole startup feel of my company.

I saw it happening right in front of my eyes in a matter of only few months.

Earlier, things were flexible, work was fun, people were even ready to put in more hours because we were all having fun. Now, work feels like work, fun is gone, frustration has become normal, and the most frustrating part is that.. WFH is now a “privilege”.

Fuck this shit man! That fucker exhausted the whole company in just a few months. Given enough time, he will be the end of this company.

I think my biggest problem is not being able to let go.

I love this product and believe in it 100%, but I CANT FUCKING STAND ANOTHER MINUTE WORKING WITH THESE FUCKING CLUELESS CLOWNS WHO ARE GOING TO DRIVE IT TO THE FUCKING GROUND!!!!!

...you know what? fuck 'em, I meanwhile reap $400+ monthly checks from Udemy, while our "best startup / amazing startup / omg wow lol i'm a fucking idiot" has earned a TOTAL of $200 in the past FUCKING YEAR

YOU FUCKING CLOWNS GET YOUR HEAD ON STRAIGHT OR I WILL TAKE THIS COMPANY OVER AND CONTROL ALL DECISIONS, IGNORING ABSOLUTELY ANYTHING YOU THINK IS 'WISE' YOU DON'T EVEN KNOW WHAT 'WISE' IS YOU FUCKS!!!!!!!

WHAT ARE YOU GOING TO DO? YOU DON'T EVEN REMEMBER YOUR BITBUCKET CREDENTIALS!!!! YOU CAN'T EVEN REVOKE MY ACCESS

AAAAAAAGGGGGG YOU FUCKING CLOWNS GODDAMMIT THIS IS SO FUCKING FRUSTRATING I CANT EVEN I NEED TO SMASH SOMETHING TO GET THE RAGE OUTAASDASDJKLFJ;KLAFDSJKL;AFDSJKL;AFES L;KADFS AF LSAFS DHI;A EGWHIOAEGW IOAEGWHIO

There's this junior I've been training. We gave him a bigger task than we usually do

"How do I link an object in table X with the corresponding object in table Y?"

"How are objects in two tables usually linked? How did you link Y with Z in the first place?"

"Em... Foreign Keys?"

"Yup"

"But there's not foreign key from X to Y."

"Well, create one. You've got full creative freedom over this task."

I sometimes feel like Juniors are either completely careless about past code or overly carefuly with not editing any past code. Frustrating but adorable

The push back phrase my manager uses when I try to discuss a requirement which I think is incorrect:
"It was discussed and agreed upon at the beginning b/n PM and engineering"
To hell with that, if 10 people arrive at a stupid decision, its still a stupid decision

I just sit back until the project progresses much further and wait for another senior dev whom they can't ignore to bring up the same issue.
It is supremely frustrating 😤

Current lappy got about 4GB RAM and not enough cores. I can't even run krita without it slowing down more the more I work on a file.
It would be frustrating if only I wasn't so depressed.
So yeah, due to being broke and lack of nerves, I'm gonna completely stop working on the comic for now.

I can't even deal with this. We just deployed a new update to our system, and everything was going smoothly. And then, out of nowhere, we started getting a bunch of error messages and user complaints.

Why do these things always happen? We spent hours trying to figure out the source of the problem, and it turns out it was because we didn't do enough testing before the deployment. Are you kidding me?

I know that testing can be time-consuming, but seriously, this is ridiculous. It's frustrating when something like this happens, especially when we're under a tight deadline. And to make matters worse, we had to roll back the deployment and start all over again. I just want to throw my computer out the window.

Uuuugghhh!

it is really frustrating not to be able to actually maintain and improve the code you're working with. i'd be happy to completely dig in and live in the code and get it all - not so much fucked up - , or, totally spitballing here, do some research on how we could improve the functionality and performance in general (which is not "nice to have", but rather ongoing customer pain points), but I'm not allowed to, because management hates having maintainable code or even an adequate number of devs. it rather has me doing hippity hoppity between different projects to make sure nothing gets my full attention. -.-

the only thing i can do is to clean it up a bit during bug fixes, but even heavy polishing won't fix this giant pile of garbage that is called our code base.

HOW

FUCKING

HARD

IS

IT

TO

DOCUMENT

HOW

YOUR

LIBRARY

WORKS

ONE

EXAMPLE

FOR

A

FUCKING

POSTGRES

CLIENT

LIBRARY

IS

NOT

SUFFICIENT

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

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

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

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

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

Frustrating...

I'm managed by idiots who don't fully realize the nightmare they're creating.

They're making small operational changes, but hundreds of them with zero evidence to back their claims up.

When I bring up how it actually works, and how operations actually work I'm told I don't use the tools as much as management does and that my feedback is limited to how I use the tool.

So now I'm just gambling that they won't fuck up too bad before I get that sweet sweet sellout money and just letting them fuck everything up they want without any warnings from me.

I'm quickly learning that the phrase of the year is, "Fuck em".

Nothing is as boring and frustrating as cloning a ripo from GitHub
run it then you get 3, 4 syntax errors
you fix them
then boom a library throws a hug ass exception

at that point I just delete the damn thing

Staging

Production

Exact replicas according to git

Of course, production is the one that doesn't work

FUCK I FUCKING HATE IT WHEN THIS HAPPENS SO FUCKING ANNOYING AND FRUSTRATING

I've been working as a programmer for 16 years now, and would say I'm not inexperienced, so it's frustrating to feel like a noob after months at a new company when they have poor internal documentation, hundreds of repos with default readme, pretty much no use of docker, sub standard equipment and use their own weird software for deployment. It's hard to meet expectations under these conditions.

Call me crazy but honestly, getting a segmentation fault in C/C++ makes my day joyful

Java or Python guys will never understand the feel you get when you end up getting segmentation fault in C/C++

Sitting in midst of nature with beer in hand and segmentation fault on screen.

WOW :) THAT'S WHAT WE CALL LIFE :)

PS: Although sometimes it's frustrating as hell

I can't share details of ongoing research projects (NDA-esque) which is frustrating because I do want to rant about them.

Let's it just be said I'm frustrated with ROS and packaged built on top of it about five times a week.

Yesterday, I was looking back at a project that isn't a focus right now, and unintentionally realised the cause of a frustrating bug. It's a one line fix and the smallest PR I've ever done, and it was such a good feeling!

Rant: i have a software firm, recently got a new project, found a freelancer to work on the project.

He is a very good developer but he works on the project only when he wishes to work and I am left to answer the clients about project delays.

It's so frustrating that I can't get angry on him otherwise he will leave the project and on the other side I have to answer clients. I am stuck with all the tensions in the world.

We're visiting the capital of my wife's home country, and it's frustrating how taxi drivers take advantage of the people. They don't use the taximeter and ask for a higher amount than would normally be. It's only here, though, because where we live it is illegal not to use the taximeter.

When we arrived at the airport and took a taxi, the driver was fined during the way to our hotel and once we arrived, he asked for 9 to 10x the price, because of the fine. He wanted us to cover the fine for him. Of course, we denied, and she gave a much smaller amount, of which I still think it was too much. If it was me, I'd just toss a smaller amount on the car seat and walk off. What'd he do? Tie us, put us forcibly in the trunk, and drive back to the starting point?

Indeed, the cost of living here is expensive, but they assume everybody is rich, especially if it's a foreigner. To be honest, I'm not even working right now, and she earns in dollars. We can afford all of this, but it's infuriating how shitty they are. It makes us want to stay in the room doing nothing until our flight back.

I hope we won't need to come back here again.

Thoughts on forced emergency support?

I am with a company I generally like a lot but there are some things I generally despise about it. Like forced emergency support.

I am not good at it, I don't claim to be.. I generally struggle with anxiety, stress and depression, I specifically avoid roles that require on-call service .. I'm a senior level software engineer.

I find it very frustrating to be expected to be on-call from 7-7 in support of infrastructure I did not architect, did not code and basically know nothing about. They provided me with a ten minute discussion about ops genie and where to find internal support articles for my training and that's about it.

Last night I received an ops genie alarm and acked it as I was instructed to do, I went around the system looking for the alarm cause and basically had no idea what to do except watch our metrics graphing praying there wouldn't be an outage. Fortunately the alarm was for our load balancer scaling operation, it was taking a bit longer than usual ... Sigh of relief. Stay up til 6am and fall asleep..

Wake up to a few messages from various people asking why I didn't do this and that and it took me every inkling of my being to remain cordial and polite but I really just wanted to scream and say a bunch of shit that would probably get me fired.

What the actual fuck?

Why expect someone that has no god damn clue what they are doing to do something like this? Fuckin shit training and no leadership to mentor me and help me get better at this role, no shadowing, no regiment ..

#confused and #annoyed

Thoughts? Am I a bitch? Is it unreasonable for me to expect my job duties stay in line with what I'm actually good at!?

Thanks.

Man fuuuuuuck, there's nothing more frustrating and scary than fucking up a local git repo. Because you know for a fact you won't be able to restore it

And I even had god damn backups of the .git folder. But reverting leaves me with more files than I started with fuuuck

I have been working on this software for 3 years now. The code base was a working prototype made by my boss before I came, not more, not less. Php + Angular. Have been refactoring a lot, backend is backed with hundreds of tests now, frontend still lacks a lot. Still a lot of programm structures are still the same weird ones my boss once created in a rush between two meetings while learning Angular to get the prototype finished. Now it's used in production which makes hard to refactor, because we have to maintain backwards compatibility. Neither the parts I added or refactored completely are satisfying, because they are built on this structures, because i never got any feedback for anything I decided and because I changed my own paradigms over time.

So I am all alone on this project. All genuinly new projects are assigned to the new team members (i was the first one, no we are five plus my boss) because I wont have time, have to maintain the old one. So I never can do something new which is quite frustrating.

I did a little side tool, the only thing I invented and did completely by myself in our repertoire - and now some stakeholder shows big interest onto this. Instead of giving me the task to make a real project from this my boss wants to give it to them to develop it. Why? Because I need more time for the main application.

Also the more the software is used the more bug tickets and feature requests come. I was crying for help for months but the others had appareantly more important stuff to do.

This might be true to some extend. Yesterday we had some kind of crisis meeting and my boss wanted again to assing pur junior to help me, who has a shit load of other things to do and is a student. I insisted that this would not be enough, and one of the fulltime devs has to get involved because the thing is our core application and I am only part time btw. So my boss said we wont decide today but one of them should do it. They should have some time to figure out who which is understandable but it's not that I didn't keep saying this for months. Now they are all like whimp whimp when I have to do php i will quit. The new projects are all typescript, with node backend if any. But alas, one of them even said yesterday he doesn't want to do js anymore. Okay... but... this is our tech stack then get another job allready?

And I should do the same probably. But then again I feel very sorry for my boss who helped me in very dark times of corona and more. If both of us leave, the project he worked on for decade (including convincing poeole, collect money..) might be suddenly at it's end while he is so exited about it's access today...

I also get insecure if it's really that they hate php so much or that they don't want to work with me personally because maybe I am a bad team Player or what?

I experienced the same at my old workplace, got left alone with big parts of the project because they didn't want to do php and js in this case and it ended up five devs doing the python backend and me doing the frontend and the php cms part all alone. Then I quit and now everything seems to happen again.

And then again I think I am only fucked up so hard by this stuff because I do not really like being a developer at all. I only do it for the money and because I am good at it (at least i think so. Nobody ever bothers to ever to read my code and give me feedback, because you know, php and js). So I guess I would hate any other job in the field maybe likewise?

This job *is* convinient, salary, office
position, flexibility could not be better. At the end of the day it's not that stressfull. And i don't have any second of freetime (due to family) or energy i could offer a new and more demanding employer, can't work over time or even take a fulltime position, can't home office, can't earn less, can't travel very long to the office and especially can't go back to school to learn something completely new. Some of these constraints are softwe then other naturally but still my posibilities at the Moment are very limited. That might change in about five years if the family situation changed. So it would most likely be reasonable to stay until then at my current job? And bear being alone with this app, don't getting involved on any new project, don't learn anything new, don't invent anything.

There was one potential way out, they considered offering me PHD position to the upcoming ml part of the project... But I learned that I would attend to a bunch of classes at university first, which i would like to, but I don't think i have the time.

I feel trapped somehow. I also feel very lonely in the Office because those fucktards keep saying in home office.

Man, I don't want to go to work today.

This is not joke but fact

More than a year ago I write code without tests, I must confess its frustrating trying to debug without proper testing. testing is painful I must admit but you can't compare the confident you have on your code with the pains when writing tests.

About a year ago I wrote a whole software without tests and this words from a friend hunted me everyday till date he said, what cannot be tested cannot be trusted. Wise words.

> colleague: My file has 79.25% of unit testing coverage
> supervisor: you're almost there! One final effort and you'll get that 0.75%!

Seeing someone this fucking dense is physically frustrating even when I'm not involved

Hello there. I'm a junior frontend developer, and I'm starting to think that IT is not for me.

Okay, first things first. This story/rant might be a bit longer than I previously thought, but whatever... :p

I started working in frontend about a year ago.

Now the problem is, that I'm absolutely rubbish with coding, and I'm starting to think that it might have something to do with my personality. While I loved (and still do) doing HTML and CSS, and maybe some JS as well, when it comes to working with frameworks, build tools, TypeScript, and all this *****, I just want to stand up and carefully smash the keyboard through the display. I can't stand the constant cryptic error messages and gazillions of config files, and don't even get me started with TypeScript. This is not how I imagined what programming is like - I know it's my fault, I was a bit naive. I still love making simpler things in HTML/CSS/JS and playing around with Linux, but I lost my will to do any of these even in my spare time. I don't have the patience to feel incompetent all the time with the promise that in a few years, doing this rubbish 8 hours a day, I will get better at it. Some colleagues even talked about it being like Lego and getting into the "flow": yeah... not in my case. There's nothing creative in this, it all feels like a factory line where I have to do the line work but also configure the machines as well...

The funny thing is, I made about the same amount of money working in less prestigious jobs. Sure I didn't like any of them, they were tiring and boring as hell, but at least they were not stressful and frustrating. I'm seriously considering moving to Western Europe and working as a bicycle delivery guy in the Alps, a postman, a waiter, or literally anything else that has something to do with the real world, and leave programming to the actual software engineers (who I deeply respect by the way).

I'll probably add more to this, but I need to go now and meditate a bit. :D

I always find it frustrating that additional requirements and changes are added and the deadline is not extended

consciously i know not to measure my worth by my productivity and that i ask too much of myself and that none of it matters, but i still struggle a lot changing subconsciously. that might be the most frustrating human experience

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.

I am embrassed.. :(

Situation was..

It was 3-4 months ago I written the process but now client was saying it is not working so I just need to update value in array..

I spent 2-3 hours everything was good..
only in the statement where I am assigning the value is not working.
I was like dude wtf call your senior why its not working .. everything is correct.. then suddenly my eyes catch the rubbish thing I did..

this is what I used mistakenly for assignment "=="

:( and I was looking at statement from 1-2 hour.. it just wasted my time

After years of working at a place where you are as good it gets in terms of domain knowledge, it can be refreshing to work with someone who has way more experience than you.

The previous company I was with wanted to have me as one of their primary engineers, and everyone else who came in would have to learn from me (most of them were low-skilled contractors). This should have been great in theory, but it was actually quite frustrating since I did not relish being the mentor figure while just being two years into my career. Despite it getting to my head at times, I was aware that I still lack a lot of skills, but with no one to teach me, I hardly progressed in terms of growth, even though the leadership treated me well and listened to me.

Took a leap of faith and quit, to join a start-up where I would be the most inexperienced (and the youngest) person. Has been a few months, and I have stumbled and goofed up more times than I like to admit, but taken with the right mindset, it is nice to see how a team of professionals goes about it. It is a learning curve to get back into the mindset of the novice (after more than a year of being the undisputed "go-to" person), and to make effort knowing that you'll fall short in multiple places by the standards here, but at the same time, it's nowhere like the frustration I felt previously when my head was pushing against the shallow ceiling.

Fun part is, the learning is almost not at all about the code, but about how to be a proactive team member and all the things to think through and finalize BEFORE getting down to code. Some of it is bureaucracy, yes, but given the chaotic place I come from, I don't really mind it as long as it only goes as far as what is required.

The most amusing part of it all to me is how I try to be humble and listen to people (everyone's got a lot more experience than me), but I'm often asked to be critical of what others say and poke holes instead of just taking what they say at face value, which has been one of the most challenging things to adapt to for me (for similar organisation cultural reasons mentioned previously)/

When the CTO/CEO of your "startup" is always AFK and it takes weeks to get anything approved by them (or even secure a meeting with them) and they have almost-exclusive access to production and the admin account for all third party services.

Want to create a new messaging channel? Too bad! What about a new repository for that cool idea you had, or that new microservice you're expected to build. Expect to be blocked for at least a week.

When they also hold themselves solely responsible for security and operations, they've built their own proprietary framework that handles all the authentication, database models and microservice communications.

Speaking of which, there's more than six microservices per developer!

Oh there's a bug or limitation in the framework? Too bad. It's a black box that nobody else in the company can touch. Good luck with the two week lead time on getting anything changed there. Oh and there's no dedicated issue tracker. Have you heard of email?

When the systems and processes in place were designed for "consistency" and "scalability" in mind you can be certain that everything is consistently broken at scale. Each microservice offers:

1. Anemic & non-idempotent CRUD APIs (Can't believe it's not a Database Table™) because the consumer should do all the work.
2. Race Conditions, because transactions are "not portable" (but not to worry, all the code is written as if it were running single threaded on a single machine).
3. Fault Intolerance, just a single failure in a chain of layered microservice calls will leave the requested operation in a partially applied and corrupted state. Ger ready for manual intervention.
4. Completely Redundant Documentation, our web documentation is automatically generated and is always of the form //[FieldName] of the [ObjectName].
5. Happy Path Support, only the intended use cases and fields work, we added a bunch of others because YouAreGoingToNeedIt™ but it won't work when you do need it. The only record of this happy path is the code itself.

Consider this, you're been building a new microservice, you've carefully followed all the unwritten highly specific technical implementation standards enforced by the CTO/CEO (that your aware of). You've decided to write some unit tests, well um.. didn't you know? There's nothing scalable and consistent about running the system locally! That's not built-in to the framework. So just use curl to test your service whilst it is deployed or connected to the development environment. Then you can open a PR and once it has been approved it will be included in the next full deployment (at least a week later).

Most new 'services' feel like the are about one to five days of writing straightforward code followed by weeks to months of integration hell, testing and blocked dependencies.

When confronted/advised about these issues the response from the CTO/CEO
varies:

(A) "yes but it's an edge case, the cloud is highly available and reliable, our software doesn't crash frequently".
(B) "yes, that's why I'm thinking about adding [idempotency] to the framework to address that when I'm not so busy" two weeks go by...
(C) "yes, but we are still doing better than all of our competitors".
(D) "oh, but you can just [highly specific sequence of undocumented steps, that probably won't work when you try it].
(E) "yes, let's setup a meeting to go through this in more detail" *doesn't show up to the meeting*.
(F) "oh, but our customers are really happy with our level of [Documentation]".

Sometimes it can feel like a bit of a cult, as all of the project managers (and some of the developers) see the CTO/CEO as a sort of 'programming god' because they are never blocked on anything they work on, they're able to bypass all the limitations and obstacles they've placed in front of the 'ordinary' developers.

There's been several instances where the CTO/CEO will suddenly make widespread changes to the codebase (to enforce some 'standard') without having to go through the same review process as everybody else, these changes will usually break something like the automatic build process or something in the dev environment and its up to the developers to pick up the pieces. I think developers find it intimidating to identify issues in the CTO/CEO's code because it's implicitly defined due to their status as the "gold standard".

It's certainly frustrating but I hope this story serves as a bit of a foil to those who wish they had a more technical CTO/CEO in their organisation. Does anybody else have a similar experience or is this situation an absolute one of a kind?

I find it frustrating to work without a mouse.

I’m struggling in studying and that’s seriously holding me back, regardless of the type of technical book I’m reading I’m always in a fight with my brain. Even if I enjoy the topic and then I’ll enjoy using what I read while I study I struggle to learn more than 1-2 chapters (sometimes even less) at time then my head starts to hurt, my focus drifts away and if I force myself to go ahead my brain just refuses to store the new informations, it feels like filling a full tank.

At this point I should have learned C++ and Swift and started to contribute to projects which aren’t overdone web apps but all I have are two half read books which silently “judges” me anytime I open my eBook library and I dread returning to having associated them to headache and frustration and the only things I read this year are design patterns (which haven’t found a single real life use since then) and F# (which I never used with the exception of some little demos and is now slowly fading away in my memory).

Have you got any study advice to help me dealing with this frustrating situation?

How fucked up is fucked up - Part 1.

What's your most frustrating moment for developing software from scratch in a start up company?

i was trying to explain to someone that we have really specific problems that others don't really understand, which i think is why devrant exists. it was kinda frustrating, cause idk if i explained it very well.

what would you guys say is the worst part of working as a dev that others wouldn't get?

Learning new stuffs can be frustrating... take it slow

In the mid-2010s, we barely had any apps in our native language and popular coupon and review sites were lackluster in our neck of the woods.
So me and some old uni colleagues got together to make a WhatsApp based "wtf is going on right now and right around here"
think Groupon meets yelp meets Google maps meet trending topics. The idea was that local business would post deals and events and people would comment on it giving stars on real time, with geolocation. So you could see what was going on right next to you, and business owners only needed WhatsApp installed to post new topics.

We... failed to go viral. That simple. Things get frustrating when infinite no-questions-asked venture capital is not available.

Then me and the other founders got very lucrative jobs in former British colonies and that was it.

This idea might still work nowadays, but it would be reeeealy hard to navigate around Whatsapp's terms of service.
Good luck to anyone who might want to try.

I hate these Mondays. You start really motivated after a nice weekend of seeing lots of old friends, but instead of your own work, you have to pick up the mess a coworker left for you while fleeing into holiday and because that's not frustrating enough, you try to review code from that new senior developer and get confronted with the probably most awful commit history someone ever managed to create.

Of course he also needed handholding and multiple trys to stop breaking like every coding convention we have for branch management...

I am still a junior and I feel pretty disappointed when being confronted with people being so..confused with stuff like git even though they have like 10 years of experience.

While I was still studying, I somehow imagined this industry to be much more...sophisticated?

I like being an employee in product development team (rather than a consultant in a project) - we're exempt from reporting hours per project and making sure to stay within budget.

But on the downside it's frustrating to se how the org happily spends development time without considering we cost money. Just found out that one department ordered a campaign site that took 4 days for 2 devs to build.
It's now ended and revenue was only a few hundred bucks.
When I asked "Didn't we lose money on this project? Considering our salaries and the ~60hour dev time"

- "Oh no, we don't count the dev team as a cost! You already work here and would get paid no matter what" 😑

Good thing I'm not in finance.

Why is it so frustrating experience to add simple websocket client to Unity? It should have been so core basic library.

I got contacted by an other company and I am so unsure whether to accept their offer or stay at my current job.

For now I spend 2 years at my current company. The culture is great and everyone gets treated very well.
The bad part is, that it is located in a part of Germany I really can't stand and to this day fully remote is not an option.

Additionally lots of stuff is really frustrating in my daily work, e.g. colleagues that experiment with critical parts if our infrastructure, resulting in every developer who made the mistake to update the local development stack being unable to work for half a day or so.

This and the fact, that our techstack sucks hard. (mostly bad php for backend and server-rendered HTML and a weird mix of Typescript, Javascript, Vue and some old bits of deprecated angular for frontend). This company has it's own product (a web platform) and no real deadlines in the sense of "something bad happens, when your team won't achieve the project in the originally proposed time"

Company number two seems to work with a wide variety of technologies for very different projects (it's a consulting compan), would pay me ~28% more than my currently raised pay and allows for full remote.

When I try to look objectively on the facts everything points to accepting their offer, but on the other hand there is this weird feeling of this being a joice that would come to soon...

How do you make such decisions? I already talked to a great colleague of mine, who thinks it might not be a bad idea to stay at the company for an additional year or 2, because I haven't yet reached the point where there is not enough to learn here anymore, which I agree on, but this company seems to offer everything I want.

I feel overwhelmed with this situation :D that's why I would like to know how you people try to tackle such a situation

Unclogging a workflow that stretches > dozen porjects, from building to analysis of build (static / lint check etc.)… Deployment.

It's frustrating.

Touching one thing and everything falls apart.

Thus small changes, fixing the rest of workflow, testing ...

Repeat .

Going now since 1 1/2 weeks. Possibly another or two weeks more.

It is soooooooo boring tedious annoyingly frustrating slowmotion shit

-.-

Working with badly designed hardware is amazing
While it is highly frustrating most of the time, I'm gonna be able to say "We can't develop software for broken hardware" to a lot of highly paid and highly annoyed peiple and that will be immensely satisfying.

We should find a way to replace passwords: any password manager which I tried is inaccurate in identifying login forms and is too hard to use for non technical people older than 40 and convince people to not use some stupid name + birth year combination as their passwords is a frustrating uphill battle.

It seems which the crazy enterprise microservice project which I'm doing (an awful distributed monolith splitted in 10+ microservices, hard to test and requiring continued context switching and running on an unreliable platform) has finally won over my brain.
It's so boring and frustrating to work with which I lost all my ability to focus, I used to be able to program well even under significant distress but more than two years of continued boredom, repetitive tasks and frustrations destroyed my motivation and with that my ability of focusing died. It doesn't matter if I'm at home or in the office, my brain is like a car stuck in neutral gear and I struggle to focus in every task.

Anyone ever struggle with tokenizers? I'm writing one by hand and it's frustrating mr so much, because at times I think my logic gets flawed somewhere inside a good loop and things get slipped or missed I don't know how to explain it.

For the first time had a frustrating day at my new job yesterday.

Been solving relatively complex issues with ease past week but spent half day on fixing glorified true/false problem that I think should be simple, still not solved.

How come complex is simple and simple is difficult?

Rant over.

Is JAXB explicitly DESIGNED to be the most brittle and frustrating API in the entire Java ecosystem? Sure fucking seems like it. Feels like every damn JDK upgrade or dependency upgrade requires screwing around with JAXB-related code, and not always in trivial ways, or a trek back into dependency management hell for a while. ARGH!!

Not having much progress with Typescript errors, it's frustrating.

I am developing a plug-in for chrome browser using python. I was trying to interact with the html page, and it was very frustrating, now I am using switching to JavaScript.
What I don't get is how did JavaScript become this power that you must use it to interact with the html page.

How do you deal when you are overpromising and underdelivering due to really shitty unpredictable codebase? Im having 2-3 bad sprints in a row now.

For context: Im working on this point of sale app for the past 4 months and for the last 3 sprints I am strugglig with surprises and edgecases. I swear to god each time I want to implement something more complex, I have to create another 4-5 tickets just to fix the constraints or old bugs that prevent my feature implementation just so I could squeeze my feature in. That offsets my original given deadlines and its so fucking draining to explain myself to my teamlead about why feature has to be reverted why it was delayed again and so on.

So last time basically it went like this: Got assigned a feature, estimated 2 weeks to do it. I did the feature in time, got reviewed and approved by devs, got approved by QA and feature got merged to develop.

Then, during regression testing 3 blockers came up so I had to revert the feature from develop. Because QA took a very long time to test the feature and discover the blockers, now its like 3 days left until the end of the sprint. My teamlead instantly started shitting bricks, asked me to fix the blockers asap.

Now to deal with 3 blockers I had to reimplement the whole feature and create like 3 extra tickets to fix existing bugs. Feature refactor got moved to yet another sprint and 3 tickets turned into like 8 tickets. Most of them are done, I created them just to for papertrail purposes so that they would be aware of how complex this is.

It taking me already extra 2 weeks or so and I am almost done with it but Im going into really deep rabbithole here. I would ask for help but out of other 7 devs in the team only one is actually competent and helpful so I tried to avoid going to him and instead chose to do 16 hour days for 2 weeks in a row.

Guess what I cant sustain it anymore. I get it that its my fault maybe I should have asked for help sooner.

But its so fucking frustrating trying to do mental gymnastics over here while majority of my team is picking low hanging fruit tasks and sitting for 2 weeks on them but they manage to look good infront of everyone.

Meanwhile Im tryharding here and its no enough, I guess I still look incompetent infront of everyone because my 2 weeks task turned into 6 weeks and I was too stubborn to ask for help. Whats even worse now is that teamlead wants me to lead a new initiative what stresses me even more because I havent finished the current one yet. So basically Im tryharding so much and I will get even extra work on top. Fucking perfect.

My frustration comes from the point that I kinda overpromised and underdelivered. But the thing is, at this point its nearly impossible to predict how much a complex feature implementation might take. I can estimate that for example 2 weeks should be enough to implement a popup, but I cant forsee the weird edgecases that can be discovered only during development.

My frustration comes from devs just reviewing the code and not launching the app on their emulator to test it. Also what frustrates me is that we dont have enough QA resources so sometimes feature stands for extra 1-2 weeks just to be tested. So we run into a situation where long delays for testing causes late bug discovery that causes late refactors which causes late deliveries and for some reason I am the one who takes all the pressure and I have to puloff 16 hour workdays to get something done on time.

I am so fucking tired from last 2 sprints. Basically each day fucking explaining that I am still refactoring/fixing the blocker. I am so tired of feeling behind.

Now I know what you will say: always underpromise and overdeliver. But how? Explain to me how? Ok example. A feature thats add a new popup? Shouldnt take usually more than 2 weeks to do my part. What I cant promise is that devs will do a proper review, that QA wont take 2 extra weeks just to test the feature and I wont need another extra 2 weeks just to fix the blockers.

I see other scrum team devs picking low hanging fruit tasks and sitting for 2 weeks on them. Meanwhile Im doing mental gymnastics here and trying to implement something complex (which initially seemed like an easy task). For the last 2 weeks Im working until 4am.

Im fucking done. I need a break and I will start asking other devs for help. I dont care about saving my face anymore. I will start just spamming people if anything takes longer than a day to implement. Fuck it.

I am setting boundaries. 8 hours a day and In out. New blockers and 2 days left till end of the sprint? Sorry teamlead we will move fixes to another sprint.

It doesnt help that my teamlead is pressuring me and asking the same shit over and over. I dont want them to think that I am incompetent. I dont know how to deal with this shit. Im tired of explaining myself again and again. Should I just fucking pick low hanging fruit tasks but deliver them in a steady pace? Fucking hell.

Why doesn't WordPress add membership system by default. It is frustrating to keep adding plugin after plugin to achieve something in WordPress. In the early days of WordPress plugins used to be free. Then developer started to charge for it per install, then they made it monthly fee which is just rip off.

I can't imagine what kind of fag would be amused to some soul defining level by the idea of frustrating a customer til they get yelled at

Fucking toad
Also hotels.com is apparently all that we have come to expect from websites in general

I'm the only one which finds really frustrating when you return to a framework or a language after a year in which you haven't used it and you're forced to Google how to do any trivial thing with it again?
It must be the 6th time I search how to do things with the C# library System.Text.Regex.

I am so sick and tired of ChatGPT being down all the time! It's like the developers at OpenAI just don't care about the people who rely on this tool to get their work done. I mean, come on, it's not like we're asking for much here. We just need a stable, reliable language model that we can rely on to complete our tasks. But no, instead we have to deal with constant downtime, error messages, and other issues that make it impossible to get anything done.

And don't even get me started on the lack of support and communication from the OpenAI team. It's like they're completely oblivious to the fact that their product is causing major headaches for so many people. I mean, I understand that developing and maintaining a large language model is no small feat, but that's no excuse for the constant problems we're facing.

I'm honestly at my wit's end with this whole thing. It's just so frustrating and frustratingly frustrating to have something that should be so simple and straightforward be such a constant source of stress and frustration. If the OpenAI team can't get their act together and provide a reliable product, then they need to step aside and let someone who can do the job properly take over.

I just hope that they're listening and that they'll take the necessary steps to fix these issues and provide a service that we can all depend on. Because right now, it's just not cutting it.

Nothing more frustrating than coming up with ideas for new apps in your head but not having a device to develop those apps on because you quit your job of which you used the provided MacBook for personal projects. But buying a new one is too expensive for just a month or two