s3b

Have a look at https://jacquesmattheij.com/due-diligence-survival-guide/ . He covers more details in the second part also.

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.

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.

Maybe the confusion is deliberate.

The US can spy on you; they just don't want anyone else to do so as well.

Great idea. Would you have any links to more things to do to improve the trust-ness of a landing page?

Priceonomics did a story on the stolen bike problem : https://priceonomics.com/post/30393216796/what-happens-to-st...

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.

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?

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.

The apple graphing calculator story - http://www.pacifict.com/Story/

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.

Not if the "handling charges" is big enough. They could end up making more money if they can sell the ticket multiple times.

You could try some of the challenges at hackerrank.com : https://www.hackerrank.com/domains/ai/machine-learning (you may need to sign up)

Also there's kaggle - https://www.kaggle.com/

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.

Have a look at "Web Operations". It deals with all the components of building and operating a large web application. http://www.amazon.com/Web-Operations-Keeping-Data-Time/dp/14...

You may want to check out Mike Gunderloys blog[1]. He was also an MS developer for 15 years before he switched to open source technologies.

1. http://afreshcup.com/about-me/

Have a looks at http://www.thoughtworks.com/radar

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.

I would recommend Martin Fowler's NoSQL Distilled : http://martinfowler.com/books/nosql.html

Have a look at http://www.bravenewgeek.com/dissecting-message-queues/

360

A good book on the topic is "Web Operations: Keeping the Data On Time"

I'd say a company retreat to some resort would be fine but to your parents place, no, unless your employees hang out with you as friends outside work.

check out http://openhatch.org/

Lets not criticize the list for being too good. Choose the subset you like and enjoy. :)

I recommend The Algorithm Design Manual by Steve S Skiena. It covers the important graph algorithms and it has catalog section of the important graph problems and how to go about solving them.

You probably won't motivate me with small amounts. As they say, "I don't get out of bed for less than $10000". :) However if you offer to donate to charity, I'll probably be inclined to help you.

How would you react if I tell you I'll only answer if you pay me? (Especially if I know you've paid in the past)