Bjorn Hansen

Senior software engineer at Hoylu. Former web and Xbox developer at Microsoft, game development hobbyist, Maker, Agile development enthusiast.

[Bjorn Hansen @bjorniac]

@unclebobmartin I'm inferring that you still set them up with CRAP and mutation testing tools, is that right? Can you give a few more details on that?

[Bjorn Hansen @bjorniac]

@vboykis Thank you for sharing this. I think you just saved me a lot of spinning my wheels figuring out a good starting setup and will let me skip straight to more interesting things. 😊

[Bjorn Hansen @bjorniac]

Liz Cheney's speech at this event is well worth watching and sharing https://t.co/oyvrXPur8e

[Kamala Harris @KamalaHarris]

I’m at Ripon College in Wisconsin with Congresswoman @Liz_Cheney to discuss how we can put country over party and fight for our freedoms. https://t.co/7zWAADzBlO

[Bjorn Hansen @bjorniac]

@editingemily A four day work week is great for preventing burnout (at least anecdotally). 🤞 That it becomes the norm soon.

[Charity Majors @mipsytipsy]

I wrote a post about the emerging generational gulf in observability tools.

O11y 1.0: many pillars, many tools, lots (but not all) are metrics backed. APM, RUM, tracing, logs, etc

O11y 2.0: wide, structured canonical log events are your source of truth

https://t.co/8tI6GZ3ZQr

[Bjorn Hansen @bjorniac]

I started working on a new game recently.

https://t.co/5NWKr9nhZt

[XBOX @XBOX]

Make his finest asset yours

Follow & Repost with #XboxCheekyControllerSweepstakes for a chance to win a custom Xbox Series X console & 2 Cheeky Controllers designed by Deadpool.‌

Ages 18+. Ends 8/11/24. Rules: https://t.co/MI0oKWl1Xf

@Marvel Studios' Deadpool and Wolverine, in theaters July 26

[Bjorn Hansen @bjorniac]

@mipsytipsy It also has this insightful observation:

"The problem with things that are implicit is that they’re easy to misunderstand, or to miss entirely."

[Bjorn Hansen @bjorniac]

@SteveDunn @alexbunardzic The in-memory test double (aka simulator) approach becomes even more valuable you write tests off the interface they implement and run the tests against both the simulator and the real implementation. This ensures both behave the same in all of the ways that you care about.

[Bjorn Hansen @bjorniac]

I launched SpaceBoots on Xbox this week. https://t.co/SRbi4R1Kyx

[Bjorn Hansen @bjorniac]

@shri_shobhit @mipsytipsy I find this to be true even if engineering activities, e.g. building vs testing software I needed to "put on a different hat" to do a good job testing what I've built.

[Bjorn Hansen @bjorniac]

I finally released SpaceBoots on Steam! Coming soon to Xbox (I hope).

https://t.co/lXqQtU9aQH

[Bjorn Hansen @bjorniac]

@kimlehtinen @kelseyhightower My family does a secret Santa exchange, so we just have one person to look for a gift for, which keeps it fun.

[Bjorn Hansen @bjorniac]

This is a great talk. Don't be a super chicken!

Forget the pecking order at work (Margaret Heffernan | TEDWomen 2015) https://t.co/aCavxERsB0 via @TEDTalks

[Bjorn Hansen @bjorniac]

@tompahoward Of course you still want to keep those PRs small and frequent to avoid merge hassle, but if your team is already used to trunk based that should be easy for them.

[Bjorn Hansen @bjorniac]

@tompahoward Go back to PR based, but don't require any review to merge. People can review later at a convenient time and nobody gets blocked waiting.

Flow is, post a PR, review it yourself, merge.

I find the self review step of aggregate commits useful for my own code

[Bjorn Hansen @bjorniac]

@ponnappa @rajatsingla_ If my commit interval is every minute or two (and it is) or shorter, this only works if I'm pairing. Sometimes I am, but not always.
Branch and merge are *so* cheap in git that I just don't see how it slows people down. Conflicts do, but those can happen on the same branch too

[Bjorn Hansen @bjorniac]

@svpino We got other benefits too, but nothing I haven't been able to get with a lighter weight process (e.g. kanban).

On most teams since then, the predictability wasn't valuable enough to be worth the cost, so rigorous scrum wasn't the right fit.

[Bjorn Hansen @bjorniac]

@svpino Anecdotally, I've been on a team for which scrum worked extremely well. What did it get us? Very good predictability of delivery in short (2 week) increments. The cost? About 10% of our time.