@retoor noone knows anymore. the knowledge was lost long ago. kinda like the one ring

@retoor the tables are created oer month sometimes per day. And if you create that it still doesn't work because there is a separate config table where you need to add the row for how long the tables exist

I am good at asking questions. Seriously clients these days want everything now and they dont even know what they want. If they know, they don't know how their current software works. So in the end I end up asking the questions noone dared to ask and everyone is acting "it's fine"
The questions usually include
"Have you considered this also affects that part of the system?" "I know it's urgent bit is this deadline even feasible?" "We have these options, which way would you like to go". You could call that requirement engineering. I call that sanity.

I work with legacy software and they overengineered it a lot through the 15 years. I only have 1 and 2 letter tags in most xmls. I don't know what they do but it seems like I don't have to.

it turns out the real reason why it is too much is that a pm already estimated this (works no longer on the project ) and they calculated that this will be x and they are now surprised that this cannot be done within the budget which was estimated by a non technical person.

Getting Indians to do it is cheaper

@lungdart ir was 3-4 month just to understand how a 4 module distributed component works, which i was assigned to. Writing tests is very hard in this distributed system because individual modules are written so that unit tests are impossible (no intetfaces no dependency injection and goto's everywhere) And prod release happens only when there is a business value added. That means if we refactor we will see if it breaks anything in 3 months when business needs something we can release.
That said in the last 5 month we managed to rewrite this distributed component in a testable way and now we have some unit tests have a system test for basic use case. But still we get surprises when something arises. And it makes me angry just how this code has never been reviewed and it kived through 13years without source control

I dont even remember how to code anymore. I am tired to declare variables and shit. I just open copilot and ask it for a method to do stuff I am too tired to think about.

Decline the call and say you are busy. meanwhile ask in chat what he wants, and that you would reply when you have time.
Hopefully many times he will write "never mind I solved it"

there are two kinds of people. who do backups, and who will.

maybe you could outsource parts of your job to a junior

react is the worst piece of library ever designed. problems start with mixing html and js and ends with infinite loops and error messages with suggestions that do more harm if you follow than your original error you are trying to solve. You can make a fine todo app with it though. I wanted to be a full stack developer with angular + .net but lately all i get is react on frontend. so I went back to backend only

@ScriptCoded they were not experienced in either case imo. but for me the question seems to be why business is using a method that is newer but has no competencies in that takes longer to accomplish over something that is out of the box and fits the project just as fine. And the only justification always seems to be that the are trying to save manual work. But in these cases they spent 100x more time on automating stuff that the work itself would have been.

@tosensei meetings was part of it, but mostly it was because I learnt how to do it along the way. But again. 1 week with gitflow and 1-3 month using trunk based, try to compare that.

Update CV of your Project Manager, send it around....

Once worked with a client. The error was that the form window was positioned wrong, when the tablet was rotated. So client asked to close the window, when tablet is turned...(implemented, deployed to prod)

react is a fucking joke. In fact the only reason i have devRant account is because i have let this anger out somewhere. I have been trying to get a decent Angular project for 3.5 years now. but no success.
the bugs in react the useeffect having 3 different uses for the same hook. infinite renders everywhere. hipster third party libraries because you can use anything you'd like. Dataflow overcomplicated. I think CTOs only think react is Great because Fb moderates anyone who says otherwise

@devTea
Backend has explicit contracts. It usually is typed and have intellisense. Your code is 90percent of the the time compilable when you hit compile.
react components when props are modified usually fail to compile and they tell you only during the compilation, not coding time.

@SirWindfield
That is what I have against react
https://devrant.com/rants/4888681/...