How to be an ignorant a**hole 101. Go to a meeting room. Pump up your meeting volume. Leave the door open so the whole floor can hear your meeting and you can diminish everyone's focus time. In case anyone closes the door, just open it again.

It's a new year. so everything stops working because tables don't exist for year 2025 in the database.

Ok so there is this company we work for as a client. They stalled the project for 3 months not wanting to sign the contract in the summer for reasons unknown while we "waited" to start.

In the contract it was noted that the project will take 6 months FROM THE time they sign the contract.
They signed it in September and still want to go live this year. They don't care what is in the contract but they have legal deadlines they must comply and for that they need the project.
I mean WAT? How disfunctional you must be to stall a project you have legal compliance for?

I hope people who store data in unstructured binary format without documenting what the the actual logic is have a separate room in hell.
I hate this legacy s***pile of visual basic code that has this abbreviated function names everywhere and the 'developer' (really should be name jack***) instead of documenting his custom solutions just thought out some custom data formats and wrote really long and bad code around it to transform and decode it. Clr sql makes it impossible to debug so wherever you are my dear predecessor I hipe you rot in hell

Company wants me to give a rough estimate of developing a new feature in a distributed legacy monolit. They told me they would inform me the next day and want the estimate on the same day for a project that will probably take 2 devs 3-4 months. I ask for more time and info, give the estimate and they say it "feels too much". I mean ok. Then why am I even estimating? If in the first place the client has only X money than do the project for X and it doesn't really matter how much work it is, does it?

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

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

So trunk-based is the new approach everyone is using, because it is so cool.
I used gitflow for the last projects with azure devops, set up the pipelines like tipically in 1 week if I had other things to do with the help of the portal clicking through things. PR-s triggered pipelines, everything worked cool.
But then trunk-based got momentum, so I worked with this client where 2 developers worked for !!!3 months!!! to setup trunk-based pipeline. It was not my money, so I did not say a thing. They were using infrastructure as code.
I am all in for automation, but seriously? Then again, another project where a DevOps team took 1 dev-month to setup the pipeline + meetings. And what do you get in the end? So that the same image goes on all environments? Like how many releases do you have for prod in a year. Lets say 24. 24 x 5 minutes of manual work for the release, that is 2 hours. So my question is why would you spend 2 hours of manual work while you can automate it merely in a month? Everyone loves to code, but using the ui on the DevOps portal saves you so much time. I don't get this. Maybe I am getting old :D

So I do not get why people use ReactJS. I hate it. for 3 years passionately. And I have to work with it every day.

- one-way data binding
this makes you write twice as much code, which will have twice as much bugs, you need to read through twice as much code from other devs.
- mixing html and JS
after all I like to pour my coffee on my omlette so I can eat and drink at the same time in the morning. This kills productivity and ugly AF
- not unified
Every dev uses their own special snowflake framework with React there is no unified way of doing things and you cannot use your familiar tools. Every project you need to start over from zero.
- Bugs bugs bugs
infinite loops, max update depth reached, key not present on list element. Let me ask you something dear ReactJS. If you know that there should be a unique key on that element. Why cannot you just put it there and shut the f up?
- works reeaally slow when compiled with TS
ReactJS was never designed to work with TS and now the tools for it are really slow. And why TS? Explicit contract is always better than an implicit contract. TS helps you in coding time, but for some reason React devs decided to worth 3 seconds to wait for compile and then realize you mad an error. ReactJS is bad and inefficient so stop making projects with it please.