Why I quit working at a startup
medium.com
medium.com
In the big corporate world you may also yourself surrounded by non-technical coordinators and developers with outdated skills -- perhaps not so much at Apple, which is a great gig if you get it. Problem with big corps is they're risk averse, so less likely to adopt trendy new tools, not hip to the latest tricks of the trade, so your surrounded by experience but not working with the latest tools and practices.
Most startups that are in their early stage don't have many developers and also don't have the funding to hire an army of developers. So they only have one expert per field.
The team that I interviewed with at Apple has 4 experienced iOS developers and this team specifically uses libraries very extensively. Mostly they have libraries that they have developer in house, but when there is something better out there they try to adapt quickly.
...all I will say is that with a company that large you're working more for a department than you are a company on a whole. I think there is no "perhaps not so much at [insert any company of 10k+ employees here]". Choose the department you work for wisely.
Great article, happy you got the job at Apple doing what you love.
a four hour commute can be mitigated (eg: work from home 3 days a week, or a mobile hotspot and pre-tax public transport commute programs, or if they want you enough a driver/moving bonus).
not having a peer to bounce ideas off of or review your code can't be mitigated.
Also I do have a hotspot, I travel by train and work during those commute hours. But because I work long hours (4+7) this leads to the second issue that I mentioned - not having enough energy to work on side projects and not being able to learn new things apart from the normal work.
btw, try Rio Adobe on de anza for lunch if you like mexican food.
The reality is that any "lead" role at a startup requires you to be the best in the room at your specialty.
> The reality is that any "lead" role at a startup requires you to be the best in the room at your specialty.
Yes, it requires you to be the best in the room, but before joining I didn't honestly know what it would be like to be a lead (and only) developer for that platform x. After working for a few months I realized that being a lead so early in my career is not what I want. I still have to learn a lot things before I cab be an effective lead and lead a team of developers.