s3b

Joined 18 years ago

Karma
531
Submissions
85
Member since
Jan 19
developer based in bangalore.
View on Hacker News

Recent submissions

Comment · 6 years ago
Have a look at https://jacquesmattheij.com/due-diligence-survival-guide/ . He covers more details in the second part also.
Comment · 6 years ago
Where did you get that from?

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.

Comment · 6 years ago
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.

Comment · 6 years ago
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.
Comment · 6 years ago
Maybe the confusion is deliberate.
Comment · 6 years ago
The US can spy on you; they just don't want anyone else to do so as well.
Comment · 9 years ago
Great idea. Would you have any links to more things to do to improve the trust-ness of a landing page?
Comment · 10 years ago
Comment · 10 years ago
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.

Comment · 10 years ago
> verify with the investors they claim to have backing from that they've actually invested in the company.

I'm curious, how would you go about doing this?

Comment · 10 years ago
But they've just wasted 1 year. They should have tried to figure out if he has the required curiosity in the first interview itself.
Comment · 10 years ago
Comment · 10 years ago
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.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton