Reply

Ohh gotcha I see what you mean - so it's actually that the map isn't initialised (still one of the annoying things Go does, you have to make(map) to initialise it), the key being unused just stops us compiling.

I do agree it'd be useful to have a way to catch uninitialised maps earlier!

 Like

Liked Andrew (@andrewt@mathstodon.xyz)
Post details
Here's the current state of the tech industry: A week or so ago I went for a big group meal and at the end they brought the card reader machine for us to pay and it had an option for us to go through an itemised bill, check some options, and pay for just those options (plus an equivalent fraction of the service charge). It was amazing! This genuinely saved us about half an hour of talking at cross-purposes and poking numbers into our own phone calculators and hoping nobody did the sums wrong and accidentally stole someone else's tip. I genuinely would consider going back there for future group meals despite the fact that I'd finished my food before Alec's arrived and he'd finished his before Darren's came, so thoroughly do I dislike the traditional bill-splitting process. And yet in terms of technology, it was nothing but a low-end smartphone running an app built entirely from OS-standard UI components. No AI, no invasion of privacy, no adverts, and I have to assume no VC funding or elaborate toolchain. Just a good idea implemented well, and genuinely we all went away commenting about how clever and useful it was. And I don't remember the previous time I experienced that. We know what people want. They want you to use the massive technological advances we've already made to build useful things that work. But apparently there's no money in that 🤷

 Like

Liked i made a very hard decision this year - live laugh blog by undefined 
Post details
a month ago i left a job i held for several years, a job that took me through a winding road of launching a product, going through an acquisition, lots of high points and lows...but ultimately i got to end the journey on my own terms, on my own time. i couldn't have asked for anything more, especially given the state of the world. i'm so very proud of my work at glitch and fastly, and it's special how i got to be one of just a handful of people who can say they have grown and lead millions of developers in creating the web and community! it was a lot of fucking work, though, and i need a break.

 Repost

Reposted Biped Earthling (@obeto@mas.to)
Post details
"Substack CEO Chris Best said he didn't want to "engage in speculation" about statements like “all brown people are animals."" Given another opportunity to answer correctly by the interviewer, “You know this is a very bad response to this question, right? You’re aware that you’ve blundered into this. You should just say no. And I’m wondering what’s keeping you from just saying no," He declined. So, fuck him. And fuck his site. I'll NEVER use Substack. #BlackMastodon https://gizmodo.com/substack-ceo-doesnt-know-if-should-ban-overt-racism-1850337647

 Like

Liked Alex Wilson-Davis (@probablyfine@tech.lgbt)
Post details
Some try to keep on top of their emails by aspiring to reach Inbox Zero. I try to keep on top of my code by aspiring to reach Branches Zero. If you're taking continuous integration seriously, you should have zero branches most of the time, and they should only exist (a) if you're not doing trunk-based development and (b) for as short a time as possible.

 Repost

Reposted Owen (spoopy aspect) (@owen@mastodon.transneptune.net)
Post details
If the Kubernetes material was honest about "your team will need recurrent annual training to remain current with this tool," adoption would crater overnight. That's not unique to Kubernetes, though it is fun to pick on them for it. _Nearly every_ significant infrastructure tool has this shape. Organizations that adopt these tools are unable to receive their value until their staff know how to use them, and that knowledge is deeply not self-sustaining.

 Repost

Reposted Marco Rogers (@polotek@social.polotek.net)
Post details
In my experience as a manager and leader, I spend a lot of time trying to get engineers to care more about business outcomes than technical issues. Not because I think the technical issues don't matter. But because I know if that if you're not trying to understand business outcomes, your judgment about the technical issues is going to be much worse. Many engineers fundamentally do not believe this to be true. And it's one of the things that sets them at odds with leadership.