burnallofit's comments

Not sure why people would take a pay cut. I just changed jobs to a remote-first company and got a raise.

Well, enjoy it, this will last about 4 months

Not to knock your experience, but imho C, Python, and Javascript are the BASIC of modern programming languages. (I don't know about Go).

Additionally, there are different levels of knowing a language. You can write perfectly workable programs in C without ever touching function pointers. So what's your level of mastery?

And then there are more difficult languages. Have you tried C++ or Scala? Ever explored the esoterical intricacies of Java's type system? Lisp? Objective-C? Kotlin? ADA?

Ok, that's languages. How about parallelism? Massive parallelism? Tight resource constraints such as limited memory? Error handling? Modern language and compiler design?

I'm not trying to say you need to know all these things to be a decent coder. My point is there are many harder problems out there and maybe if you're bored you might want to try working on some of them.

Early 50's here. I am switching jobs now, I'm at the top of my game, and getting the biggest money I've ever made. There are several factors, I believe. First, keep up to date. Certain things are really popular right now and therefore attract the best pay, and more jobs are available. Second, be in the right place. For example, SF Bay Area only has so much housing but has a lot of companies who are hiring, so they are competing for the people who are here. Third, project confidence because you are in fact awesome because of all the cool shit you've built. If you walk in to interviews resigned to making less money or a taking a step down, I bet you'll find that actually turns out to be true. Fourth, on a regular basis (once a month or so) you should be having conversations with your manager about your career and next steps, and taking time to work on getting there.

One more protip. At a higher level, moving up further does not mean being a better coder. It means talking to people (often on different teams), thinking and generating ideas (and applying for patents), sometimes taking risks to prove those ideas, figuring out how to improve process, and generally communicating. If you believe you're not good at any of these, you can actually study and practice them and get better at them. I did, and it's working out for me.

Depends on the experience level of the interviewee. If they are fresh out of school I expect them to know algorithms and data structures and maybe some specific topic they studied at an advanced level (like compilers, db, graphics, etc). If they are 5-10 years into a career, they should have a lot of knowledge about whatever it is they've been doing. If someone says they have 5 years of Android programming, I'm going to ask them a lot of Android API questions as well as Java.

In either case, there are questions that have multiple difficulties of responses. The more experienced/capable they are, the more nuanced and complete their answers will be. For example, ask a Java person how GC actually works. Most people have very little idea, but the best talent knows a good bit more.

But there are other variables. I've known perfectly intelligent and productive coders who took months to build a really complex well architected system that didn't solve the business problem and hence were a bad hire.

I'm looking at that Google report link and it says, for 2017 Tech, 39.2% asian, 53.2% white, whatever that means.

It's worth mentioning that for 2017 leadership, the Google numbers are significantly different: 26% asian, 68% white (and 75% male). So the decision making is still quite white and male.

I'm currently an MBP user (and have been for several years). But I find myself not using the keyboard and screen that often, most of what I do is shuttle between home and office where I have better keyboards and larger screens. The mini looks like an interesting option because it can take more RAM than MBP, and is smaller/more portable. For those few times when I actually need a portable screen and keyboard, it may be possible to use an ipad pro for that, might be worth checking that out, or some other solution may be out there. Likewise on the MBP, I seldom actually need a battery, so I feel like I'm paying a huge premium for the laptop form factor.

That said, I can afford the MBP; as a professional, one shouldn't cheap out on tools that help you get your job done efficiently.

... with what kind of warranty? included software?

Care to compare market caps of those ultrasound manufacturers with that of Uber?

Depends on the stocks. Yesterday some went up, some went down.

This doesn't make sense.

"Engineering force pretty much has no negotiation power in this." Of course we do. We don't have to accept an offer unless it meets our terms.

"Engineering is a liability. Sales is an asset." This is ridiculous. In an early stage startup, most likely there is no product. Sales has nothing to sell if not for engineering's efforts.

"VC's won't allow it." If a startup can't hire, then VCs have exactly nothing.

This isn't to say that cash isn't a good thing. I personally agree that options need to be balanced with cash, especially when a startup is well funded, and options are fractions of a penny, but that decision is individual.

Source? I believe you, just would like to see for myself.

This, and it deserves to be underscored: IW/AJ continue to enjoy every single bit of 1st Amendment protection that they did before these bans.

This is not a reason to not ban IW. If anything, it's a reason to ban it sooner.

CEOs didn't decide this in a vacuum. Many of their customers and users and shareholders don't want to be associated in any way with IW.

I don't think Alex Jones knows how to code.

And if he used an existing infrastructure like AWS, I would hope AWS would kick him off of it.

... a nut butter?

<I'll see myself out.>

Many public corporations want to (indirectly) maximize taxes. That's because taxes are levied on profits, and maximizing profits to increase share value is often a good thing.

It totally depends on the company you work for.

I work for a company whose stock is going up. This makes it a great company to hold stock in. Unless, some other company's stock is going up faster. Which there always will be, but I don't necessarily know which one. I could be making more money. The trick is knowing which, unfortunately reading tea leaves is difficult.

So I diversify. I leave some money in my company, I put some money in other investments. That way, if my own company goes down in flames, I am not totally lost, and if they continue going up, then I gain.

What you need to do is understand your company, its products, its history, likely future, and risk factors. Yes that is a lot of stuff to research, but it is the way to sleep better at night while feeling good about yourself and your investments.

The point is that subs and carriers were far, far more effective than battleships.