grigjd3

This is largely true in any field.

I mean, know what you're walking into, but if you have that, then yeah. My family makes me risk averse. No complaints. Happy as is, you can chase after whatever, as long as you're vaguely relevant in the field.

I don't get it. This guy can feel free to not listen to podcasts. It's not killing music by any stretch of the imagination. I still find plenty of bars and restaurants that annoy me with having a local band play that I don't really want to listen to. There really is nothing forcing you to identify and listen to podcasts.

The difference is the supporting documents found by Qualcomm during discovery. Internal Apple documents stated that Apple was actively trying to portray Qualcomm's patents as inferior by going to other providers.

Where do you work, so that I know to avoid it? Documentation needs updating as things change.

Maintaining checklists in documentation for software design reduces mistakes dramatically. Writing step-by-step exacting build instructions for one of our core products reduced the annoying requests for help I got dramatically.

I'm glad you found the writing style pleasant. I found it grating and self-indulgent.

A shrink-wrapped version of the instant API that could be installed on a server would be a good product.

Associations came very late to Mathematica (version 10 if I remember right) and the whole of the tools in Mathematica had to be converted over. The result was incomplete.

I don't know what planet you live on, but there is plenty of publicly owned property that I have no access to. If you think otherwise, just try randomly walking onto a military base that does not allow visitation. You may argue what you feel is morally right, but any actual adult has realized that morally right does not equate to the law.

The lack of comments is a problem. The rest seems whiney to me, but sometimes I need to leave notes for other developers as reminders.

Your health insurance company listens to you? Mine just constantly tries to wriggle out of paying.

Don't know why someone is entitled to a particular career. Change can be hard but I certainly wasn't ever promised an easy life.

I have my doubts. Maybe a bootcamp can prep someone to make apps (though I know very little about mobile app development), but at least in my job, I need a pretty in-depth understanding of how technology works. It's not enough to have used Spark a few times but I really need to know what it's good at and what it lacks and I need this understanding across all my tools. I need to know at least the basics of the implementation and to have that understanding across all my tools, I have to have a pretty strong theoretical grounding that I just don't see the bootcamps providing. Like maybe a few really bright people figure that out while in bootcamp, but I suspect most don't.

You were able to find documentation? Where do you work?

So I've worked with AWS and with our internal clusters as a dev. My experience has been that I have to make work-arounds for both, but at least with AWS, I don't have to spell out commands explicitly to the junior PEs.

EDIT: I should be clear, our PEs are generally pretty good, but because their product isn't seen by upper management as the thing which makes money, they're perpetually understaffed.

I was particularly entertained by the tax forms this year. The 1040 is now only half a page, but there are several other required forms that didn't exist last year.

So I work in a cheaper location for one of these companies and while I get paid a bit less, it's so much cheaper to live here that I can pocket a lot more.

I find Big O to be useful when designing solutions just to be able to quickly decide what data structures are appropriate for a task, though, admittedly, this doesn't come up that often.

I think the worst experiences are always what stands out in peoples' minds.

I find Google to be a useful index of documentation. I'll often search something like `java documentation <name of class>`.

I worked in numrel before and was even offered a tenure track job focused on teaching. I didn't want to work 70 hour weeks though. Now I focus on my family and data pipelines seem like a nice hobby.

So I strongly suspect that for people who will leave over the open office, there already exists better reasons for them to leave.

Presumably, the demand the business sees justifies the cost of workers. Of course, layoffs happen.

Open offices aren't about worker happiness or efficiency. They're about decreasing costs.

You can hear toilets flushing? Yuck.

The visual simile is, of course, not perfect, but the simile is not provided for people that knowledgeable on the science in the first place. If you happen to find a more appropriate simile that people follow, please make it known.

So, avoiding the discussion of what constitutes best practices, it's important to recognize that you don't know everything (which you seem to get), but also identify the things you don't know and learn how to research them enough to handle your task, which is definitely more than Wikipedia but most often you don't need to be an expert in a thing. Unfortunately, if you don't have people around to grade your work, developing a sense of this can be quite hard.

So the natural sciences aren't universally bad. My PhD advisor in relativity was a terrific guy to work with and I saw him as a friend and mentor. The problem is that the supply of people seeking PhDs, post-docs, and tenure track jobs in the natural sciences so far outstrips the available jobs (often a hundred to one) that there is little natural pressure to suppress bad behavior. In fact, the assholes tend to thrive because it turns out that taking advantage of others can get you ahead.

Certain fields have an easy path to the private sector, like computer science, but a lot of academic research is done by academics because the private sector would never pay for it. Certainly when I left academics, I didn't see many employers looking to study initial data for the binary black hole problem. ;)