5 ms·
I'm always surprised at how much push-back this one gets. The point I was trying to make here is that you DON'T need to be someone who spends every free moment
by simonw 3y ago
I'm always surprised at how much push-back this one gets. The point I was trying to make here is that you DON'T need to be someone who spends every free moment blogging, writing open source code and so on. Stick up a few posts somewhere and leave them there, as a tiny piece of extra evidence that you're someone who knows how to do things.
Maybe part of the problem is that I'm grossly under-estimating the amount of work involved in "post an interesting technical article to it once or twice a year" for people who don't already spend a lot of their time writing.
- dleeftink 3y agoIn spirit, I agree–spread your knowledge, far and wide. But making your voice heard and stand out from the crowd is no simple feat: we don't all have the luxury of Twitter following, a much subscribed RSS feed, a prominent domain name to spread the fruits of our hard work. The network effects that benefit early influencers are difficult to pierce, I find.
- simonw 3y agoThat's the trick here though: you don't need any distribution at all for this to work. You just need something you can link to from your resume, so the hiring manager can click through and see a tiny bit of evidence that you can talk about code or build a project.
- dleeftink 3y agoI hope it'll pay off. In the mean time, how to keep motivated when much time is spent publicising to little public response? Asking for the proverbial friend.
- OJFord 3y agoFor me the barrier has been that I've never gotten around to setting the blog up. Often having ideas for (I think) a good post, but don't have the blog to post it to. Some of them get noted down in case I ever do. I do intend (as in, have been particularly intending recently) to do it, because I think then I would find it lower effort, I would do it, and that I would like that. We'll see, the list of things I've intended to do is long! I particularly like the style of (others') blog where you dive semi-deep on something semi-obscure to fix or do something, perhaps it's not your usual area, and then write up a nice explainer for the next searcher, or a note to self for the future. Explain it to someone who's never understood it before, while you still remember that perspective.
- simonw 3y agoSuggestion: start with Gists! Post markdown files on https://gist.github.com/ https://gist.github.com/ - you can migrate them to a proper blog should you set one up in the future. I'd suggest a regular repo, but GitHub block search engine crawlers from indexing anything other than the README.md file - so Gists are weirdly better for publishing content.
- ajb 3y agoI think you answered your own question. It's hard to get into writing if you don't do it regularly.I literally have a list of 30 things it would be nice to write up (not all technical) but the chances of my doing it alongside everything else are quite low.
- rmorey 3y agoI appreciate the advice Simon! I don't think that you're under-estimating it, I think many (myself included) have a tendency to over-estimate it. I feel a decent amount of self-induced pressure for anything I think about writing to be really high quality - I see blogs like yours and the standard is set quite high! But I understand this is true of many creative activities: if you have good taste, then reaching the level of the work you admire is necessarily a lofty goal, and your early creative work is unlikely to meet it. But all of that is to say, the best course of action is still to Just Write. I hope I can take this advice to heart and start putting work out there! A 20-year blog begins with a single post :)
- maerF0x0 3y agoAt least for me, I've never had my public projects, blog, youtube tutorials, stack overflow contributions etc referred to. Generally it's been easy for me to get interviews, and hard to get offers (something like a 95% onsite rejection rate). I have enough experience and the resume items that gets recruiters excited about their next bonus. But it seems folks walk away saying "Yeah he's technical, but <xyz nitpick or undermining statement about my contributions>" ... Oh well, I've also given up on caring.
- kyleyeats 3y agoMy take on the problem: You're projecting yourself onto other people who are looking at candidates. This stuff matters to you but not to most people hiring. The corporate apparatus tends to view these things as a challenge to The Way We Do Things Here, so a blog post or side project might even be a red flag. This strategy is a gigantic waste of time. It shouldn't be but it is.
- simonw 3y agoYeah, my advice is very much focused on "working for ambitious technology companies". I wouldn't be at all surprised to learn that standard corporate coding jobs - where the interviewer might not even have a technical background themselves - wouldn't even think to check for a GitHub profile or technical blog.
- JadeNB 3y ago> The corporate apparatus tends to view these things as a challenge to The Way We Do Things Here, so a blog post or side project might even be a red flag. I know I'm coming at this from the idealistic position of someone who's lucky enough to have a job, but isn't it kind of a good thing if you find out early that you're applying to a company where doing things is a red flag?
- nsxwolf 3y agoYou'll never receive feedback on why you were rejected either way, so there's no way to prove or disprove this strategy, or any other. We hem and haw and tweak and fret about every little thing in this process, but ultimately all roads lead to "Thank you for your interest in SomeCorp. Unfortunately, we have decided not to proceed with your candidacy at this time, but we appreciate the time and effort you dedicated to the application process. We will keep you in mind for future openings and we encourage you to keep current on new opportunities on our careers site."
- jakelazaroff 3y agoI don’t think the rejection reason matters in this context, though. GP’s point is that it’s better to filter out fundamental mismatches before a protracted interview process that ultimately results in a rejection anyway (or, worse, an acceptance that results in quitting or being fired).
- CharlieDigital 3y agoOne of the best ways for me to understand a candidate in an interview process OR a prospective lead that I'm reporting to (be it CEO, CTO, VPE) if I'm on the other end is to see how they think and how they interact with a community. Whether that's through a blog, through their socials, LinkedIn posts, through their YouTube, through their GitHub - I review all of it; anything I can find. I want to see how they communicate, how they think, how they comment their code (or don't), their view points on various touchy subjects in software engineering and system design. It's basic background research. Why suffer through a relationship that isn't going to work out for either party if some basic digging can short circuit that problem? It also provides great context for an interview and points of discussion that help connect with the other party.
- sanderjd 3y agoI think this is not a good idea. It is misleading to dig into what people are like in their personal lives in order to understand what they're like in their professional lives. People have different personas in different situations and for different audiences, and what matters as an employer is what they are like professionally, which may or may not have anything to do with what they're like on social networks or youtube.
- richiebful1 3y agoI generally agree. The public presence that's given me a lot of positive attention is: 1. Having a custom domain 2. Using that custom domain for email 3. Have your custom domain point to a professional-looking page. Maybe link to a resume/other things. I've had a surprising number of interesting interactions just because someone saw my email and went to my website. Some yielded job leads and eventual referrals to jobs through old-school networking.
- sanderjd 3y agoDo you think the TLD matters? I see you have a .com, but I can never find any plausible .coms available for my name. Do you think people care about this? Does stuff like .me and .io seem unprofessional somehow for this "cool, they have a custom email domain, let's go see what's on it" workflow?
- simonw 3y agoIn 2023 I don't think the TLD matters at all. As long as you don't have an offensive term in your domain I doubt anyone would blink twice.
- _jal 3y ago> I'm always surprised at how much push-back this one gets. Oh, but the explanation is simple. They resent being told to eat their vegetables. They know you're right, but don't want to or can't do it, and attack you for reminding them of that. > I'm grossly under-estimating the amount of work Probably a big part of it - if you write a lot, it is very easy to forget how intimidating it can feel to those who don't. And related hang ups can be amplifiers - if you don't write much and have insecurities (sorry, "imposter syndrome"), being told this should be an easy thing can be triggering. And this is employment we're talking about - it is definitionally high-stakes, whatever the stakes are.
- rconti 3y agoI don't think there's anything wrong with your suggestions; I think they absolutely will be minimal effort for a huge payoff for a job seeker. Here are the struggles I've had with this over my career: * Public vs private persona. I'm a pretty open person and happy to share with people I know or where it feels "safe" (eg, Facebook where I more explicitly control the audience) but I'm deeply uncomfortable with publicly announcing things under my name on the internet to go god-knows-where. This is one reason I've been tremendously uncomfortable with Twitter. I absolutely despise the public-broadcast model, and I'm somewhat suspicious of people who want to make such a show of themselves (to build an "audience"). I've toyed with various forms of pseudonymity but that brings its own problems; I think it encourages antisocial behaviors and then at some people you have to 'expose' yourself (eg, when you have to tell your prospective employer, yes, NSAhacker31337 is my github, take a look!) * Along with the above, blogging/demonstrating things always has a bit of a show-off feel. "Look at this great thing I know how to do, I bet you don't know how to do it!" Or, worse, you're demonstrating something "everybody knows" and you look like a naive fool. * Consistency. I've made various "I should start a blog" efforts over the years, and inevitably get bored of the tools and want it somewhere else, or I don't like the tone I used to use, or I forget which site I used, or whatever. It's sort of like how "just go to the gym 3 days a week" shouldn't be that hard, but for 99% of people is. Again, these are just my personal struggles, to maybe help you understand why people don't. It's nothing against your advice, which I think is fantastic.
- sanderjd 3y agoWow, nailed it. This is exactly how I feel.
- simonw 3y ago"Or, worse, you're demonstrating something "everybody knows" and you look like a naive fool." That's one of the reasons I'm so keen on the TIL format - it gives you permission to write about tiny little things (things you just learned) without feeling like you need to be original or explain something groundbreaking and new. I just published a tiny one about figuring out typing.Protocol in Python for example: https://til.simonwillison.net/python/protocols https://til.simonwillison.net/python/protocols I wrote more about that here: https://simonwillison.net/2022/Nov/6/what-to-blog-about/ https://simonwillison.net/2022/Nov/6/what-to-blog-about/
- mihaic 3y agoI think what you're missing is an explanation on why there should be any correlation between being a good developer/employee with writing a blog. Sure, you can say communication skills, but you want to test for that anyway. I actually think that we'd have a much better job market without any of this. I'm also among the people that see too much pointless content being published simply for hidden advertising, including by companies.
- simonw 3y agoI don't think there's a correlation between writing a blog and being a good developer. I think there's a small correlation between "having a tiny bit of evidence online that you're capable of solving problems" and "getting invited to an in-person interview" - at least given my own experience at the companies that I've worked at (and hired for). That said, I do think there's a strong correlation between being good at written communication and being a great senior / staff-level engineer.
- clbrmbr 3y agoI’m not a big self-publisher myself, but as a hiring manager, I am definitely attracted to candidates who have a robust public portfolio. That said, in hindsight, I’m not sure I’ve noticed any correlation between the strength of the public portfolio and job performance.
- sanderjd 3y agoHa, I think this is a pretty classic description of unconscious bias; you have warm fuzzies about people with robust public profiles, without having given much thought to whether it's a strong signal of performance. Edit to add: I feel like this came off as harsh, but it really wasn't intended to at all. We all have this kind of bias. I have a bit of the opposite bias as you, for what it's worth, because the best people I've worked with have been essentially silent in public, and I tend to see people with robust public profiles as having spent time on marketing themselves that could have been better spent on other things. This kind of bias that we all build throughout our life experience is why hiring is extremely fraught.
- sanderjd 3y agoI think you nailed it in your last paragraph! I have about five ideas I really want to write about, that I know would be really great future PR for myself in the niche I'm interested in right now. They wouldn't need to be long, but they would still be hard for me to write and edit to a point that I feel good about having them out in public attached to my name. So they don't get written. (But maybe they will someday.)
- feoren 3y ago> Maybe part of the problem is that I'm grossly under-estimating the amount of work involved in "post an interesting technical article to it once or twice a year" for people who don't already spend a lot of their time writing. I think that's largely it. I've thought of things that would be interesting to write as a short blog post. What's stopping me? * I don't already have a blog where it'd be easy to post things. I'd have to research what to sign up for. Free sites would spam my readers with ads that I don't agree with, and try to track them. Paid sites cost money, obviously, and may be predatory. The platform could be acquired and/or killed, and I could lose my content or have to transfer it somewhere else. I anticipate 50% of my total blogging effort would be spent just on dealing with all this bullshit. That's time I could be spending with my kids. "Just self-host!" okay now 90% of my total blogging effort, plus server costs. * I'd want proper code formatting, examples, good visuals; you know, something publishable. I'd simply never get it good enough to post. Perfect would absolutely be the enemy of good. And ideas are constantly evolving and changing. I don't agree now with everything I wrote a year ago; that's what progress and learning is supposed to do. So the temptation to constantly go back and nitpick it, edit it, would be there, all day, every day. * Nobody would ever read it anyway. It wouldn't hold a candle to the blazing light of SEO spam. Even in the unlikely event someone did read it, they wouldn't care. Even in the unlikely event they did care, it would be different from the way they're already doing things, and therefore they'd become extremely hostile and write hateful comments about some minor point they misunderstood. Which I'd read, despite myself, and then I'd have shower arguments with them instead of focusing on actual work. So why am I doing all this work? Who am I blogging for? A potential future employer for the one time I'm looking for a job in the next decade, who probably won't even bother to look at it? "You write for yourself, to organize your own thoughts" -- okay, I already do that, I just don't publish it, for all these reasons.
- Capricorn2481 3y agoI'm not a blogger and have no horse in the race, but I think you should re-evaluate a couple things on the list if you think you'd be interested in blogging. For both #1 and #2, there are dozens of static site generators that handle all of this for you automatically. Not all of them are as complicated as the big ones. You can get started with a theme in Zola in a couple hours and that can be your blog forever, with support for code syntax. For number 3, the idea is not that people will organically stumble on your blog in a search, but that you'd share it to different communities relevant to your blog post. If you're writing about F#, post it on the F# reddit. SEO spam can't really mess with you there. In fact, I feel like SEO spam is only pushed by Google, and communities tend to not engage with that content. I feel you on the extremely hostile responses, though. Without fail, any article that makes it to the top of HN has lots of people insinuating it was somehow written maliciously, even if it's just about something minor like Sum Types vs Union Types. Unfortunately the answer is to shut off your brain to the hostility but take in their counterpoints. These people likely think about nothing but code for most of the day, so even if they're well-rounded and nice in real life, their brain has temporarily narrowed the scope of their world view, and they make mountains out of mole hills