1,790 karma · joined July 29, 2010
I think you'll be hard pressed to find anyone who believes that ensuring all of the servers are running the same code is a 'premature optimization'.
http://imageshar.es/4ed7bbc343641e6c1e000dc1
Why even include a link in the email if it brings me to a page that just lets me know I can't do anything from there?
Have you tried loading: https://news.ycombinator.com/?
EDIT: I don't really know why I'm being downvoted for this. Wouldn't you switch apps too if you relied on google voice for your text messages and you couldn't log into it anymore without it instantly crashing?
I can only assume that there's some desire within Google to make sure the iPhone versions of their products are complete dogshit to try and encourage Android adoption.
Get out. Now. I spent about 5 years in a job that initially taught me a lot about a lot of different technologies, but I peaked very quickly. I felt like I couldn't leave, however, since I was easily the most technical and was responsible for lots of disparate systems. So, I would go to work and spend 95% of my day chatting on IRC and 5% of my day writing a solid chunk of code that made it look like I was busy.
The biggest regret I have is that I spent at least 2 years too many at that job before I grew the balls to change my life. Don't waste another day of your life rotting away in an environment that's doing nothing for you.
Full disclosure: I work on this!
I don't know why these articles keep getting written. No one's forcing you to write your tests first, and if you can't wrap your head around the benefits (which the author clearly can't) then don't do it. It's fine. I'll still continue to utilize TDD, and continue to pump out significantly more code (with significantly less bugs) than the code I produced without TDD. Yes, there's definitely code I write where I don't write the tests first. It happens, sometimes it's just easier to bang something out because you aren't sure what you're building. That doesn't mean TDD is a failure, it's a tool, like anything else. Use it where it's appropriate, because the benefits are massive.
It's ok that you have a different mentality, but understand that it's just that, a different mentality. Some people enjoy the hustle and bustle of building organizations more than lounging on tropical beaches for the rest of their lives.
https://github.com/LockerProject/Locker/blob/master/Ops/webs...
And tends to end with around 40 lines of checking URLs and other various bits of information to know which middleware can be chained in, and in which order that doesn't cause them to conflict with one another.
If Strata can solve this mess, then it's definitely a step up in my opinion.
Also, re: #9 - see http://memolane.com/ or http://lockerproject.org/
If you're interested in ways to track and parse through all the types of data that you're producing, take a look! We're probably about a month away from a hosted offering, but you can pull down the source and run it yourself today.
Those are not the people we're discussing. Those people aren't deciding whether to work 9 to 5 writing java for an insurance company or go work for a startup as employee #1. Yes, you can make lots of money consulting. I spent a year doing nothing but consulting. It's mind-numbingly painful work. Apples to oranges.
But what you will find is startups that are willing to offer their early employees wages fairly close to market rates (though to be fair, we don't know in this situation whether the person in question's salary was near typical market rates, we just know that he was deciding whether to take a 50% cut in it), which is (if I'm reading correctly) what the article is suggesting people look for rather than settling for shitty wages and delusions of Facebook-level growth.
I think you'll find this is much rarer than you think. Most startups, especially YC companies for what it's worth, are offering exactly what's mentioned in this article at that stage. While it's totally ridiculous, it's currently the state of the world. Sure, it sucks, but asking for 20% is going to get you laughed out the door.
Also, the advice is just wrong. No startup is giving away a 20% equity slice to their first employee after they've already raised a round. The chance of a startup even creating a 20% options pool for employees hired after series A is slim, and even slimmer is them giving their entire pool to the first employee. You're essentially saying you expect nearly the same equity slice as the people who invested their time to validate the market and build a prototype, which is absurd.
I'd love for someone to prove me wrong by pointing out a startup that's given 20% to their first employee after raising a seed round.
EDIT : To clarify, the dude in the original post is definitely getting screwed, but this is way too far in the other direction to be at all useful.