261–270 of 396 posts
Are you an embedded developer? Bring a show-and-tell to your next interview. Bring an example of something you've worked on. Doesn't have to be in a finished case. In fact, a raw PCB can be more effective. Make sure 1) the product has already been released to the public and 2) the hardware isn't stolen. Rig up a small power supply and find a way to light it up. Being able to drop that in front of an interviewer and e…
Earlier quoted context omitted.
I hear something like that from other Americans as well and do not doubt that what you are saying is true, but why is it like that? Isn't the unemployment rate in the US low (around 3.5%) right now? I live in a country where the unemployment rate is pretty low (2.5%) and the situation is kind of the reverse of what you are describing. Companies are trying to entice potential employees, not the other way around. Give…
Its very easy to fire people in the US, so there is likely considerable more stress involved in the US workers day to day as they don't know if they are going to be randomly let go tomorrow. US companies will often lay off hundreds of people to make the bottom line look better. We generally make good $ but it could all end tomorrow so we are always thinking of the next position. In addition, we get used to the money…
I was not sure how this worked. I knew that the US does not have universal health care (not having it is one of those famous American things) but I assumed that it works on a private basis - you chose an insurance company if you want (and can afford) to be insured, you pay them $X per year and you are covered. Having this tied to your employment gives your employer terrible leverage over you. That would certainly stressed me out.
100%. Especially in a tough, competitive job market like today's, having a credible portfolio of work, published content, and external validation makes a huge difference. It can take a good candidate to the top of the list, and when that list is a few dozen great applications, that's critical. As a hiring manager I weigh a candidate's public presence at 10~15% of my initial decision, even more if it's exceptionally i…
Earlier quoted context omitted.
Your blog post: > Got another programming job. Got fired for "performance." I think the reason wasn’t good, but I also have a hard time building a theory of mind, which means I can’t read code written by others. If you can't read code written by others, that's going to be a big concern for companies that require you to read and modify other people's code. Perhaps you need to be a contractor, not an employee.
Yikes! https://gavinhoward.com/2023/04/rust-is-dead-to-me/ > Rust the language is dead to me. > why? > Because, quite literally, the Rust Foundation wants to make people like me unwelcome in any Rust event, not just official ones. > Don’t believe me? > Look at the draft Rust Trademark Policy that the Rust Foundation is asking for comments on and go to page 12: > > We will consider requests to use the Marks on a case…
Frankly, I think if people won't hire because of a post like this, then the interviewers are the one contributing to the problem.
Are you an embedded developer? Bring a show-and-tell to your next interview. Bring an example of something you've worked on. Doesn't have to be in a finished case. In fact, a raw PCB can be more effective. Make sure 1) the product has already been released to the public and 2) the hardware isn't stolen. Rig up a small power supply and find a way to light it up. Being able to drop that in front of an interviewer and e…
Basically no one I've ever met was able to show me work from the giant corporation they worked for.
But it's not because of NDAs. Indeed because of the nature of my business, those companies are my customers, we already all work together, I've signed NDAs, they are actually permitted to show me stuff.
It's because they didn't do anything. NDA = Not Doing Anything.
> That alone will get you 80% of the way to the job.
Large corporations (500+) employ like half of Americans, and probably way more than 50% of tech workers. So many of their management systems boil down to having 2-10 people redundantly doing the same work. So many do no work. I mean I'm sure they aspire to do work, but there isn't any to do.
As long as this remains the norm, your interviewers will, statistically speaking, have done similarly little as you, and that will be okay, and leetcode will prevail.
Are you an embedded developer? Bring a show-and-tell to your next interview. Bring an example of something you've worked on. Doesn't have to be in a finished case. In fact, a raw PCB can be more effective. Make sure 1) the product has already been released to the public and 2) the hardware isn't stolen. Rig up a small power supply and find a way to light it up. Being able to drop that in front of an interviewer and e…
This reminds me of one of my coworkers who was interviewing around for his next job. One company he was interviewing for had a website with public facing user profiles. My coworker found a SQL injection vuln and wrote a POC virus that would spread to any other account that was logged in while viewing an infected profile and took it with him to his interview, gave them the code, and showed them how they could fix it.…
Unfortunately doesn’t sound like a scalable application strategy
Earlier quoted context omitted.
This. I got a very mixed feeling after reading his blog. On one hand it looks like he lacks self-awareness to the point that he didn't realize the blog makes him quite unemployable. On the other hand, I don't want to live in a society where a blog can make you unemployable, and I kinda admire his audacity to keep it on.
Oh, I quite realize my blog is a liability. My original post was refuting claims that a blog and public code could get you hired. I know that companies will see me as not a good fit. That's a good thing for both of us because I've come to realize that I'm not a good fit for a sterile office environment.
A blog can get you hired.
Your blog will not.
Earlier quoted context omitted.
I have to say that that part in Rust Trademark Policy also gave me a stop. It's just so weird to single it out.
It's good PR CYA. They ensure that there will be a much lower chance of an article headlined "mass shooting at rust conference" being written. I am personal'y of the opinion that brands play it too safe in general and people aren't stupid and know that just because a brand happened to be near something bad doesn't mean the brand is responsible and therefore bad, but apparently brands don't agree and they're the ones…
I don't think this follows. Historically speaking, most mass shootings have occurred at locations that specifically disallow firearms, making them "soft targets" where the cowardly attacker will not have anyone fight back. It doesn't seem logically consistent to assume that this policy item has the effect you are stating.
The act of taking a serious look at people's github repos, blogs, or whatever else, appears fairly unusual. I've asked.
This sounds like good advice. My current employer does not allow me to write technical blogs or have public git repos even if they’re unrelated to work and when done on my own time with my own resources. Sigh.
> My current employer does not allow me to write technical blogs or have public git repos even if they’re unrelated to work and when done on my own time with my own resources. Sigh. That sounds like overreach; I don't think an employer is within his rights to try to restrict what you do in your free time with your own resources and without infringing on your employer's legitimate claims to IP (copyright, trademarks,…
The hilarious thing about their no open source policy is that they sometimes shoot themselves in the foot. Sometimes, they’ll hire someone with a very successful open source project, in the employment contract ask them to stop working on it, then part of the company depends on that software and when it breaks, it causes chaos because the maintainer now works at the company and had to stop working on that open source project that the company relies on.