dankoss

Apple is a hardware company, and you can't WFH using giant anechoic chambers, laser cutting machines, electronics labs, and who knows what else. The products may be manufactured overseas, but there is a lot of expensive hardware needed for designing, prototyping and testing.

I get that Apple does a lot of software these days, but one of the things they are also known for is tight integration between the hardware and software, which doesn't happen without them working side by side.

There may be a significant fraction of employees that can work remotely, but it would significantly change the culture of the company to split the workforce like that.

I agree; I tried standalone boxes like the Electribe 2 and Circuit, and the iPad with Korg Gadget is just way more flexible and quicker. The soft synths available are truly equal to desktop apps now. DAWs like Cubasis and Aria are way more powerful than the OP-1s abilities, although I still feel like the workflow could be improved.

I've only seen this as an internal move, which is how I did it. Ask to take ownership of a project, even a small one. Do it successfully for at least one delivery. Learn the technical ins and outs and the political relationships within the organization. Become known as the $PROJECT person. Every organization handles projects differently so learn and use the specific lingo and process in yours.

Once you do that, you can formally ask for the role.

You mean to say they should have courage?

One way to think about this is traveling to places where connectivity is literally unavailable -- national parks, mountains, etc. Your boss cannot prevent you from traveling to those locations, so even if you aren't somewhere where you are unreachable, why should you be expected to be available?

Most of my bosses have left their contact information for when they are away from the office, but I've never had reason to use it. I would feel bad interrupting someone's time off except in cases of true emergencies, which might happen more often in other company cultures or industries.

I think it's because at the top level, everyone already has perfect grades so schools need additional criteria to limit their selection pool.

Totally agree. I believe Agile works well in environments with shallow tech stacks, but it has worked terribly in my experience in product companies that build hardware, FPGA dev, embedded software, and other disciplines that can't deliver on two week increments or increments that align well with other disciplines.

This is not strictly true. Health insurance has always been available for purchase by individuals, and the ACA expanded access to this by providing income-based subsidies. When you lose your job, you lose access to your employer's subsidy and risk pool.

That doesn't change the fact that heath insurance and healthcare is expensive, it's just pointing out that the only way most people can afford to have it is because their employer is paying for most of it. If that cost was more transparent to salaried people, it might spur a more useful conversation about how to bring down the cost of healthcare.

I second this, it's a great cross-platform scratchpad.

I have talked to several interviewers with a buying mindset, and the thing that annoys me the most is that they always ask why I want to work for $COMPANY_NAME, especially if it's a well known SV company.

They don't understand: I don't need your job, your recruiter called me, so what is it $COMPANY_NAME has to offer me that's better than my current senior level gig?

Agreed, though have you seen Garageband on iOS lately? It has inherited quite a few features from Logic like the drummer, more customizable plugins / inserts, etc. Also, Cubasis and Auria are pretty powerful. Still not as powerful as Logic proper.

Every other manufacturer of battery powered devices, including laptops, does CPU throttling based on battery degradation, and doesn't mention anything about it. It sounds like you were just looking for an excuse to jump ship.

I like it, I use my custom domain as a spam filter and have a short me.com address.

I have a "wireless" thermostat (Honeywell Redlink) and there are a lot of problems you have to think through to make it work. In particular, what is the failure mode when the thermostat can't communicate with the furnace? What if your internet goes down and it can't communicate with your phone? You might need a different failsafe for when it's 0C vs 25C outside, but what if your exterior temp sensor stops working or can't communicate with the furnace? Not to mention the security implications of having an appliance on your network.

All these problems are made much simpler with a wired thermostat and battery backup. I wish it was easier, but in this case "smart" doesn't really buy you much energy or UX savings over a simple programmable wired device.