Sabbatical week one is complete, and I’m finally finding some time to blog about it! I had a pretty active week. It started with hurricane preparations as Dorian burled toward Florida, however in the end we suffered a very light glancing blow. In short, we got off easy. The Bahamas did not get so lucky, however, and got pretty messed up. I’d love for you to take a moment to donate to their recovery here: https://www.
One of the most amazing perks of working at Stack Overflow is the sabbatical. After 5 years of FT employment, you are entitled to 20 paid days off (outside of normal vacation) that you can spend however you please. My sabbatical officially begins on Tuesday (as Monday is a holiday). Practically speaking, I am out from Aug 31 - Sept 30, returning to work Oct 1st. This is an amazing opportunity and benefit, and I can’t thank Stack Overflow enough for how well they treat employees.
In this post I’d like to show you how I ported an Azure Classic Cloud Service application (which cost me $16 USD a month by the way) to a .NET Core Azure Function, and now host it in Azure for $0 a month! That’s right - Azure Functions are both awesome and (usually) free! Introducing realDonaldTron So back in late 2016, when our dear leader was elected president, I decided to have a little fun at his expense.
It’s been a while since I changed things up, so I decided on a new Twitter handle and blog domain. This site is now hosted at davidhaney.io and called “David Haney” which in my opinion is a much better (and more descriptive and maybe even more egotistical) domain than haneycodes.net and the old name of “Haney Codes .NET” Don’t worry - haneycodes.net deep links will redirect properly for years to come, so you won’t miss anything at all.
A few weeks back I wrote this tweet: I did a presentation / speaking thing last week that got me thinking: would it be useful to blog about how to build a resume as someone new to tech, from the perspective of a hiring manager? I might whip that up today or tomorrow if people like the idea. — David Haney (@haneytron) July 9, 2018 43 likes later, it’s clear to me that this topic is in-demand.
Well I failed badly in my mission to blog every week of 2017. I guess life and stuff just got in the way in the end. I’ll try to be more consistent in the second half of 2018. Anyway, I bring some news: I have a new blog engine, and we are hiring at Stack Overflow! New blog engine I was previously using WordPress but had many issues and concerns with it.
This post is for those of you who hire developers, and also junior developers who want to be hired. Let’s talk about how developers are just like individual stocks in the stock market. Time for a little role-playing: you’re now a stock market investor. As a financial advisor, your company has given you $2,000,000 USD to invest in the stock market. It’s made very clear that the future of the company depends on the return on investment (herein called ROI) – “gains” – that your investments bring to the company.
In case you missed the big news in the industry this week, a GitLab employee accidentally deleted a ton of production data and took their platform down for hours. It was only when everything was on fire and they were in deep trouble that they turned to their backup systems… only to find that none of them actually worked. Backup Prod Data Regularly Not exactly a groundbreaking statement, right? Everybody knows this.
In part 2 of my series on dev team interactions, I’d like to talk about conducting good code reviews. Most dev teams will find themselves in a situation where code reviews are necessary, and in my experience many do them very poorly. I’ve even worked in companies that had such a negative code review culture that people left the review sessions upset, even considering quitting. With a few easy adjustments, you can quickly learn to conduct excellent and positive code reviews with your team.
As a developer working for a company, you probably work on a team. The interactions on these teams are sometimes pleasant, and other times hostile. What’s interesting to me is that a lot of the time, a hostile interaction could have been a pleasant one if only approached differently. Hostile teams are created by the actions of the people on them, not by the situations they encounter. One such hostile action is blame.