Sodman

You definitely don't need a personal website, blog, or even github for most jobs. If you're cold-applying to jobs online, and you don't have a linkedIn it will be seen as a red flag by some hiring managers - easier to lie/exaggerate about employment history, durations, title inflation, etc. Also more likely that you might be trying to work multiple jobs at once. LinkedIn doesn't need to be fully fleshed out with a ton of content or even any activity, but just a public list of companies you've worked at, rough timelines and titles, is enough to reassure most hiring managers.

The product page linked at the top of the article boasts about voice encryption as a feature, but that's still very much illegal on ham radio bands in the US, right? Or is it just referring to CTCSS/DCS?

IDK they're like $19 these days and that's without even knowing if they'll officially list the Vision Pro as a supported device yet or not!

https://www.apple.com/shop/product/MM6F3AM/A/polishing-cloth

solo.io | Senior Backend Software Engineer | Boston, MA (Cambridge), or fully remote (NA) | Full-time

Solo is an application networking company working with open source, cloud native technologies. If you are passionate about technologies like containers, Kubernetes/k8s, Istio service mesh, Envoy proxy, GraphQL, Cilium, eBPF, WASM (server side), serverless functions, and more, then Solo.io is the place for you! We strive to productize the bleeding edge of cloud technologies, contribute back to the open source community, and build solutions which scale globally. If you're interested in presenting your work at conferences and meetups, that is also encouraged and supported (although not mandatory!). We are a golang shop. Prior experience with k8s operators, Envoy proxy, or service mesh technologies is a big plus.

Apply here - https://boards.greenhouse.io/soloioinc/jobs/4329288005

Or see our other openings - https://www.solo.io/company/careers/

I think "bad people" is relative here though. The incentive structure is entirely misaligned. As mentioned elsewhere in the comments here, agents' best strategy for the highest possible payout is trying to close as many deals as possible, not taking the extra time to find each person the ideal perfect fit house (volume over value-add quality). It sounds like you found an agent who went the extra mile to get your business, which is great for you! But I suspect that there are other, less buyer-friendly agents out there out-earning your agent because they just drop the "difficult" customers and work with the easiest-to-close folks to get more overall commission.

Given that, my personal strategy when buying was to just do as much of the legwork as possible myself, rather than risk leaving due diligence to somebody whose financial incentives are not aligned with my own. My agent essentially ended up mostly relegated to docusign-forwarding duties.

Ok but you could replace the "Sending notifications about new listings in real time" duty by subscribing to zillow/redfin etc with specific filters... for free. It's hard to make the argument that that's worth 6% of a of half million dollar purchase? I agree it's a part time job to be a buyer in this market, but I don't think the buyer's agent really makes that job much easier in my experience.

"Answers a call at any time of the day" is definitely a great nice to have, but I suspect that puts your particular agent in the top 10% of the field. Most agents I have used will just let all phone calls go to voicemail and then text back or call you back hours or days later. YMMV a lot on this one.

The problem in this particular case is that the sensor may be confidently telling you there's something in the way, but in reality it's just a plastic bag. Hard braking at 70mph on a highway as if you were about to hit a concrete wall is probably not a great outcome in this scenario if there's somebody behind you.

The issue is that the number displayed on the dash can be toggled between "% battery remaining" or "miles remaining". The "Miles remaining" is actually "EPA rated miles x % battery remaining", and NOT "miles remaining based on last 10 miles driven, or current navigation destination".

If they removed the 'Miles remaining' number and only showed a percentage, you would end up having to do the exact same conversion in your head anyways. "Oh I have 43% remaining of my 330 mile battery, how much is that?" so this is really just a quick shortcut.

Tesla has a separate screen with very clear range estimates that the user can toggle (based on last n miles or based on current exact 'instant' reading). In addition, when navigating to a destination, the nav tells you the estimated battery % on arrival, which is also based on current driving and is generally quite accurate. In addition, it will tell you during & after the trip exactly why the estimated and actual range differed. Eg "0.5% extra battery used due to a 5.6mph headwind, 2% extra battery used by driving over 70mph", etc.

Having a count-down 'Miles remaining' on the dashboard doesn't always make sense, particularly when you haven't entered a destination, or if you're switching between highways and back rounds a bunch. Either way, it's never going to actually be accurate down to the last mile. In reality, you just have to know that the miles on the dashboard are "EPA miles", meaning if you're driving on a flat surface in good conditions at ~55mph, that's what you'll get. If you change your speed, or conditions get worse, you know you'll need to adjust it in your head (or use the dedicated in-car screen to automatically figure it out for you!).

I always disliked Irish (and languages, in general) in school. However, now that I'm over a decade out of college I find it to be one of the few subjects I wish I'd paid more attention to when I'd had the chance... Sure, it's not particularly useful in adult life, but neither is organic chemistry, for most folks.

The main difference for me is that it's relatively easy to "fill in the gaps" for any other subject we learned from the ages of 12-18. Irish however, is niche enough - and learning resources generally technologically behind - that it's still quite tricky to self-teach or "quickly google" answers to things. That makes it unique from most other primary/secondary school subjects which are more universally taught across the world.

One use case I'm psyched about for this - shared virtual whiteboarding for remote workers. No traditional apps have been able to reproduce the feeling of being in the room with a small group, collaborating on a shared whiteboard, feels like a huge opportunity!

+1 for BetterSnapTool. I've had it for years, one of the first things I install on any new Mac. It's always "just worked" for me, zero issues.

I would 100% watch the Kitboga of ssh attacks, is that something that exists today? The closest I've seen so far is password purgatory - https://www.troyhunt.com/sending-spammers-to-password-purgat...

solo.io | Software Engineer | Boston, MA (Cambridge), or fully remote | Full-time

Solo is an application networking company working with open source, cloud native technologies. If you are passionate about technologies like containers, Kubernetes/k8s, Istio service mesh, Envoy Proxy, GraphQL, Cilium, eBPF, WASM (server side), serverless functions, and more, then Solo.io is the place for you! We strive to productize the bleeding edge of cloud technologies, contribute back to the open source community, and build solutions which scale globally. If you're interested in presenting your work at conferences and meetups, that is also encouraged and supported (although not mandatory!). We are primarily a golang shop, although no prior go experience is required. Prior experience with k8s operators and service-mesh technologies is a big plus.

Apply here - https://boards.greenhouse.io/soloioinc/jobs/4026989005

Or see our other openings - https://www.solo.io/company/careers/

Why not both? They don't have to be mutually exclusive!

For example - I'd be in favor of abolishing the current H1-B lottery in favor of taking in the first 85,000* applicants with the highest paying job offers. Maybe have some carve-outs based on sector, weighted by demand, so eg academics aren't competing with SV-tech salaries. Not a perfect solution, but solves a lot of the major problems we have today.

*I also think we should increase the cap

I was going to say that FANG companies don't make up a very large proportion of H1-B visas and that the majority go to Infosys, Tata, Cognizant and the like... But I just looked it up, and it turns out that trend has been reversed considerably in the past few years, which is great to see!

2016 numbers - https://h1bgrader.com/reports/sponsors/lca/2016 2022 numbers - https://h1bgrader.com/reports/sponsors/lca/2022

As of May 2023 there are[0] over 300,000 tech job listings open and unfilled across the country.

There are an additional 65,000 H1B visas available each year to applicants with bachelor's degrees in STEM, and an additional 20,000 degrees available for those with masters degrees in STEM. So those +85,000 individuals wouldn't even cover one third of the currently open positions (and notably, more positions are opening every day right now, where the cap is only renewed annually).

[0] https://www.computerworld.com/article/3542681/how-many-jobs-...

In reality the bar to clear this requirement is quite low. E.g. "We put an ad in the (physical) local newspaper one time for this job, with every single esoteric skill this individual has, listed as hard-requirements..." is typically sufficient to check the box and say "We've tried, nobody applied!".

solo.io | Software Engineer | Boston, MA (Cambridge), or fully remote | Full-time

Solo is an application networking company working with open source, cloud native technologies. If you are passionate about technologies like containers, Kubernetes/k8s, Istio service mesh, Envoy Proxy, GraphQL, eBPF, WASM (server side), serverless functions, and more, then Solo.io is the place for you! We strive to productize the bleeding edge of cloud technologies, contribute back to the open source community, and build solutions which scale globally. If you're interested in presenting your work at conferences and meetups, that is also encouraged and supported (although not mandatory!). We are primarily a golang shop. Prior experience with Envoy, Istio, or k8s operators are each a big plus!

Apply here - https://boards.greenhouse.io/soloioinc/jobs/4026989005

Or see our other openings - https://www.solo.io/company/careers/

I don't think the problem is the subscription model exactly. If I'm paying $15 / mo for netflix, it's very clear that my $15 gets me one month of access, to whatever's available in their library at the time. Similarly, if I pay $10/mo for Gym access and the Gym decides it no longer wants to do business with me, that's fine because A) there's more Gyms for me to go to, and B) I never had any expectation that anything from that Gym would be 'mine' forever, it was always an ephemeral access to the service conditional on my recurring payments.

The problem is for services where I pay a la carte to build a "personal" library of things, like steam games, Google Play movies, Amazon Kindle books, etc. I've paid a one-off price for the digital content with the expectation that I will have access to that content indefinitely. If I am abusing the platform, causing issues for others, or generally and blatantly violating ToS in a major way, then I think that's a different story. But if I need to dispute one transaction, then the ability to immediately remove all access to previously purchased content immediately, indefinitely, and frequently without review or appeals - is very anti-consumer.

It effectively nullifies existing consumer protection laws. I will never issue a chargeback or complaint against Valve (Steam) or Google, even if I have a perfectly legitimate reason to do so - as loss of those accounts after all of these years would likely be more costly to me than most erroneous charges I'm likely to see.

The problem is that your accounts with these businesses can accrue innate value over time. If you have spent 4 figures on buying video games on steam, and then want to dispute a fraudulent charge, access to all previously purchased items can be suddenly and permanently revoked. No to mention data like friends lists, game saves, etc.

Even worse, for XL companies who force one account across multiple products, the two things can be completely unrelated. If Google is refusing to RMA my pixel 7 phone which arrived defective, I can't issue a chargeback on that phone purchase because they'll remove my access to the last 10 years of family photos, my email, my domains, and my GCP servers.

Sure you could argue that this is the exact reason you should diversify these things across different companies, but in some cases the tight integration between these products is a compelling feature. The price for that feature shouldn't include removing consumer purchase protections.

solo.io | Software Engineers | Boston, MA (Cambridge), or fully remote | Full-time

Solo is an application networking company working with open source, cloud native technologies. If you are passionate about technologies like containers, Kubernetes/k8s, Istio service mesh, Envoy Proxy, GraphQL, eBPF, WASM (server side), serverless functions, and more, then Solo.io is the place for you! We strive to productize the bleeding edge of cloud technologies, contribute back to the open source community, and build solutions which scale globally. If you're interested in presenting your work at conferences and meetups, that is also encouraged and supported (although not mandatory!). We are primarily a golang shop, although no prior go experience is required. Prior experience with k8s operators is a big plus.

Apply here - https://boards.greenhouse.io/soloioinc/jobs/4026989005

Or see our other openings - https://www.solo.io/company/careers/

The author touches on why it matters in the article - either you have to restrict hiring to folks who are already rust experts (much smaller hiring pool, also usually meaning higher comp expectations) - or you have to consider the cost of training new/existing staff on Rust. Rust has a notoriously difficult learning curve, especially to folks who don't have a background in C/C++. As the author mentions, you may be looking at 6+ month ramp up time until new hires can comfortably write non-throwaway tech-debt free production code. For many startups looking to iterate quickly, that's just too slow.

Conversely if you are looking to hire Java folks, you'll have an enormous pool to pick from, or if you need to train somebody in eg Go - you can do that significantly quicker than you could with Rust.

You have to remember though that coding interviews != production code. Taken to the extreme, are you also adding logging, metrics, performance benchmarks, etc?

TDD is great if you can get it working in a tight interview time schedule - they can also reveal any misunderstandings of requirements before the actual solution is implemented!

On the flip side however, many interviewers have experienced countless folks who spend the majority of the interview time on tests and setup, only to run out of time on delivering the solution to the actual presented problem. When I feel like somebody's spending too long on these things I'll try to nudge them towards wrapping up the tests and moving onto the solution. You would be surprised though by just how frequently it's met with open hostility, by candidates with only 10-15 mins left in an hour-long interview and no solution started!

solo.io | Software Engineers | Boston, MA (Cambridge), or fully remote | Full-time

Solo is an application networking company working with open source, cloud native technologies. If you are passionate about technologies like containers, Kubernetes/k8s, Istio service mesh, Envoy Proxy, GraphQL, eBPF, WASM (server side), serverless functions, and more, then Solo.io is the place for you! We strive to productize the bleeding edge of cloud technologies, contribute back to the open source community, and build solutions which scale globally. If you're interested in presenting your work at conferences and meetups, that is also encouraged and supported (although not mandatory!). We are primarily a golang shop, although no prior go experience is required. Prior experience with k8s operators is a big plus.

Apply here - https://boards.greenhouse.io/soloioinc/jobs/4026989005

Or see our other openings - https://www.solo.io/company/careers/

It's hard to give specific advice without a resume, but I did want to comment on the '8 years experience / 4 year degree / mid-20s' combo a little. You may of course be the rare exception here, but broadly here's what I've seen with that kind of resume:

Many hiring managers will all but ignore any high-school level work. It's a nice positive signal to know that you've been interested in this kind of work for a long time, and stuck with it. However, I've seen many resumes that will claim "3 years" worth of experience before entering college, and when you dig in it frequently boils down to "I edited a few html pages for a total of < 100 hours when I was 16". I'm not saying that's necessarily the case here, but unless you have demonstrable projects on your resume from that period that prove otherwise, I'd probably avoid counting those as "years of experience" on an application.

Many hiring managers will even discount college internships, as the quality can vary significantly. This is less likely to be the case for you as you have that FAANG AAA brand recognition. I've also seen candidates do two 3-month summer internships and count that as "2 years experience" though, so you have to be careful about that.

Ultimately, some managers will see that you graduated in eg 2019 and therefore bucket you in with other applicants that have ~3-4 years experience. Nobody will believe a fresh 21/22 year old graduate getting their first job after graduation credibly has "5-6 years experience", for example.

Some may also see and accept 8 years experience at face value, but then they'll judge you at that level and compare you to other applicants with 8 years post-college experience. These days that includes many other folks from FAANG companies with equally impressive resumes who were recently laid off. Maybe the resume screener notices that you didn't make it to a certain level within 8 years (senior/mentor/manager/tech lead/whatever arbitrary metric they expect somebody with 8 full years experience to have achieved), which could be an elimination criteria for some. Finally, as many others have commented coming from FAANG usually implies a very high salary expectation, especially for folks with 7-8 years experience, so many companies likely literally can't afford you!

Couldn't agree more. Not even just in the skills cloud section, don't put anything on your resume that you're not ready to talk about in an interview. It's baffling the amount of candidates that answer questions about their resumes with "Oh it was so long ago I don't remember" or "Oh it was just a quick 2 week R&D spike that was never shipped".

If something was a long time ago, just summarize it and keep it short and sweet. Nobody needs to read 8 bullet points on an internship you had 7 gigs ago which has no relevance to the job you're applying for. Contractors are particularly bad offenders here in my experience. No hiring manager will read through a 13 page resume for somebody with 6 years experience. As the TFA mentions, use that valuable space to highlight more recent, relevant experience and put your best foot forward. Everything else is just noise.

I get that it's still a candidates market (especially for strong candidates like OP who can get 11 offers from 13 full attempts), but the spreadsheet of questions you should be asking a company linked in TFA has some eyebrow raising notes and unreasonable expectations imho.

For example - there's a big pushback that any hiring manager worried about a candidate who don't have required skills they could learn in 6-12 months is "quibbling". Is this a generally held belief? In the startup space in particular, most folks I interview frequently have consistent < 2 year stints at most if not all of their prior companies. Expecting a 12 month ramp-up time on a particular piece of technology needed to do the job would be an immediate no-hire from me. If I personally joined a company and couldn't meaningfully contribute for the first year, I would consider that a complete failure and expect to be let go. Do other people feel differently? Perhaps this expectation is more applicable to larger companies than startups?

In Finland, Denmark, The Netherlands, and Sweden, the income distribution ratio[0] of the total income earned by the top 20% of earners vs the bottom 20% of earners is about ~4x. Denmark has a personal income tax rate of 56% [1]

Best data I could find[2] after a quick google on USA puts income distribution ratio around 5.2x, so not much of a substantial difference in gross income disparity vs USA at the 20th/80th percentiles. Personal income tax rate is about 37%[3], so certainly USA lets you keep more of your paycheck than Denmark.

So high earners in US are making ~20% more than their peers in Denmark relative to the bottom 20% in their respective countries, and folks in the US pay ~20% less tax as well.

Certainly it's a notable difference but we're not talking orders of magnitude here, especially since the above math doesn't account for all of the benefits that higher tax rate brings, both tangible and intangible.

However, when we're talking in absolute numbers, most Danes out-earn most Americans. The median wage in the US is ~$52k [4] vs Denmark at ~$72k [5], which closes the gap even more.

I suspect there are significant differences and outliers at the extremes however, and that is likely where most of the VC money lives - whether we're talking about angel investors dropping >$100k or VCs spending millions on pre-revenue companies. I'd wager we're well into the top 1% of earners in the US doing the funding. This is the most likely explanation to account for the differences in early stage investments and growth opportunities you described above, imho.

[0] https://tradingeconomics.com/denmark/income-distribution-eur...

[1] https://tradingeconomics.com/denmark/personal-income-tax-rat...

[2] https://dqydj.com/average-median-top-household-income-percen...

[3] https://tradingeconomics.com/united-states/personal-income-t...

[4] https://www.averagesalarysurvey.com/united-states

[5] https://www.averagesalarysurvey.com/denmark

I have FSD Beta. These uncut youtube videos were a large reason of why I bought into FSD Beta, and I will say they show it in a much better light than my on-the-ground experience. I'm not even accusing the posters of selecting only good videos to begin with (although I'm sure that's also happening) - but the videos really don't do justice to the "in the car" feeling.

As a specific example, when the car suddenly slams on the brakes, especially at slow speeds, it doesn't look like a big deal on these GoPro cameras - but it feels like a much bigger deal when you're in the car and you feel the g-force of your body reacting to the sudden unexpected deceleration. Some of the more transparent and honest reviewers like "Chuck Cook" even add an overlay showing these forces in real time on their videos - but seeing a number briefly spike is a very different experience than feeling it live.

I would say FSD is getting closer to "safe" (not there yet though imho) but it's still very far away from "comfortable".

solo.io | Software Engineers | Boston, MA (Cambridge), or fully remote | Full-time

Solo is an application networking company working with open source, cloud native technologies. If you are passionate about technologies like containers, Kubernetes/k8s, Istio, Envoy Proxy, GraphQL, eBPF, WASM (server side), serverless functions, and more, then Solo.io is the place for you! We strive to productize the bleeding edge of cloud technologies, contribute back to the open source community, and build solutions which scale globally. If you're interested in presenting your work at conferences and meetups, that is also encouraged and supported (although not mandatory!). We are primarily a golang shop, although no prior go experience is required.

Apply here - https://boards.greenhouse.io/soloioinc/jobs/4026989005

Or see our other openings - https://www.solo.io/company/careers/