The tools, libraries, frameworks etc. we have now make it a lot easier to build something that would have earlier cost a fortune in custom development. If anything, it's getting cheaper to build projects now.
Mostly it's because I'm facing a problem I don't know how to solve. And I'm expected to somehow predict when it'll be done.
Another scenario is when I'm asked for updates but in reality the status hasn't changed. And I can't say so because that would imply I've not done anything even though I've been busy searching for a solution.
More software outsourcing to places where the work can be done cheaper.
Now that wfh is becoming common, companies will start to realize that if most of their employees are working remotely, then they might as well hire from cheaper cities or countries.
I would say don't give up. Use your second probationary period to learn and improve as much as you can. If things don't work out well, at least you would have learnt something useful you can use in your next job.
Try asking the seniors for help when you get stuck somewhere. But only ask for help after trying all the possible solutions you can think of yourself.
Try to come up with 3 or 4 test scenarios for your code and test them before you submit the code. Thinking up new scenarios will help you reduce the bugs.
Critically review your own code a few days after you've submitted it. Pretend it was someone else's code and think of all the possible ways to improve it.
If your seniors are willing, ask for a code review. Go through the review comments carefully and make sure you never get the same review comment again. Don't ignore any comment, however trivial it may look.
Spend an hour or two extra everyday to improve your knowledge of the system. Learn something new everyday about the tools, language etc.
You really shouldn't fire someone after just 90 days. Maybe you should try moving the person into a different role/team before firing. Or at least give them some more time. 90 days is way too little time to pick up new skills and domain knowledge.
It could be for performance reasons - maybe there's an in-memory cache with only the recent threads kept in it. Commenting on an old discussion would involve loading the thread from disk which would be expensive. Hence comments on old threads are disabled.
I want a transparent process where I know in advance what I'm getting into. I'd like to know how much they're willing to pay(the range) and what exactly I would be expected to do - the role as well as the product I'd be working on. I'd also like to know about the interview process and how long after an interview I'd be told the result (preferably immediately). Also tell me about the sort of people I'll be working with - team size, roles, backgrounds etc. Once I have that information, it's easier for me to decide on whether to attend the interview or not.