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.
> 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.
Does your team allow for knowledge buying tasks? For example, if our team needs to implement a continuous integration solution I might suggest to first create a research task to evaluate the tools available. Once we have that knowledge we can choose the best option for us and create the task to implement it. The way you can sell this is by saying, "I can give you an estimate now but I'll know a lot more after a few hours researching the problem. If you give me that time then I can give you an estimate with a higher level of confidence."
> Another scenario is when I'm asked for updates but in reality the status hasn't changed
I've struggled with this as well. Especially when the person asking for the update is not technical and therefore has a hard time relating to the complexity of the problem. In this situation your instinct may be to tell the person what you think they want to hear. Something like, "I'm figuring out the solution and should be done soon." I know it's uncomfortable but you are better off being honest about your progress. Tell them that the problem is more complex than you initially thought and you are having to do more research to find the right solution. Don't forget that research is part of the job so looking for solutions is doing work. Don't feel bad about that.
With that being said, there is nothing wrong with asking for help from other developers when you are stuck. Asking for help is a sign of strength. It is good to try solve problems on your own before asking for help but do not drive yourself crazy. I have spent far too long banging my head against the wall looking for solutions. These days I am much more comfortable asking for help.
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.
People think this is similar to the outsourcing trend of the past. No this is bigger than that. The big difference is that in the past there was a difference between outsourced vs working from the office employees. This time there will be no difference. All employees will be the same and employees will be employed based on merit to the company without any stigma.
Also, it's going to be a long time before we go back to normal so companies will need to adapt. Once things change to work from home first it will be hard to go back to an office only work environment.
But that's part of my point, people will be hired based on their abilities and how much they contribute to the company now. That was not necessarily the case in the past. And the reality now is that there are parts in the US that have a low cost of living that are now open for people to work from.
I know that I would be willing to work from a low cost coast city if I only need to show up to my office 1 or 2 times a month. I'm even willing to get paid a bit less.
Yup, top notch engineer will always get paid well but most salaries will fall. 1st the engineering pool will increase both due to the distance between employees and employers not being a big obstacle and more people who can choose it as a career will choose it. 2nd engineers can now live in a lower cost community and will be willing to settle for a lower salary.
As always employer will look to pay the least so they will do their best to push salaries down when ever they can.
But keep in mind it will still be a well paid job when compared to other careers.
To the average person AI makes everything sound more modern, "smarter". So it gets sprinkled in everything. Things that have been using the same logical algorithm since the dawn of computing are now called AI. The worst is hearing people in the field calling every piece of automation and single purpose code that does one thing the same way every time as "AI".
Everyone does it just to attach their old or boring tech to the fancy new trend and have some "cool" rub off on them.
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.
As mooreds wrote, I'd start with Edgar and the SEC. I'd also check state records (i.e. are they a Delaware C corp? I should be able to pull public information about the filing, same for most states at varying levels of difficulty).
I used to get annoyed at all of the chest-beating press releases about how much money a company had raised until I realized it was a form of external validation. None of the companies which burned me on equity/funding issues wanted to talk publicly about their fundraising rounds, it was always "we're going to a do a press release, it's just not the right time now". If you publicly state "We raise a $2.5MM Series A from the following investors" I can go out and verify that.
Bonus story: a "company" recruited me hard to be their CTO. Some wining and dining. But a lot of handwaving about the business model and where the funding was sourced from. The founders wanted me to bring their "vision" of social e-commerce to market utilising a proprietary algorithm which would be disclosed to me only upon taking the role. When pressed about corporate structure and funding they eventually disclosed that funding was coming in the form of personal checks written to cover bills as they came in, by the domestic partner of one of the founders. No C Corp, not even an LLC. I declined.
