Writing bugs @amazon. 🇧🇪 Living in 🇨🇦 | Opinions my own 🙃 https://xitter.cf/t.co/ReLdZEbDjh
Toronto
Joined December 2011
- Tweets2.9K
- Following423
- Followers425
- Likes2.5K
Pinned Tweet
The #gophercon agenda is online 🎉! Join me for some functional programming with Go on November 13, at 10.25AM EST 😄
gophercon.com/agenda/session…
#golang
Dylan Meeus retweeted
Nerds, tune in next week!
I'll be with Penny de Byl (@penslayer), Dylan Meeus (@DylanMeeus), and Jasmine Greenaway (@paladique) answering your questions.
linkedin.com/events/celebrat…
Dylan Meeus retweeted
Best Picks for #Golang #books #Gophers #godevelopers
Don't forget to share your thoughts and reviews! Mention me, and let's hear the community's take on these gems.
2/2 #readingcommunity
My “author interview” for my book “Functional Programming in Go” is out! partnerships.packt.com/inter… 😁
And the book itself is also ready for pre-order on Amazon 😎packt.link/TFhFS
Just seen the new Dr Strange movie and I can’t help but wonder.. are there some serious fans of Mortal Kombat involved with this one? 😅 Definitely expected to hear a voice shout “Fatality!” In some fight scenes 😆
Websites that limit password length to 16 chars like @clearlyca … why? Saving a few cents on storage? 😅
Definitely miss attending FOSDEM in person! Also guess I have to wake up earlier now with the 6hr time diff 😅
Dylan Meeus retweeted
Generics.
Fuzzing.
Software Bill of Materials (go version -m).
Workspace mode (go.work file).
15% ARM64 performance improvements with register ABI.
Reduced garbage collection overhead with pacer improvements.
And so much more!
Go Go Go 1.18 #golang
“Go 1.18 Beta 1 is available, with generics” 🎉 🎉
— go.dev/blog/go1.18beta1
This is a huge step for Go, with a ton of work behind it. Thanks to everyone who helped us get this far. Huge thanks to the team here, who did a lot of heavy lifting.
– @_rsc
#golang
Dylan Meeus retweeted
"I Would Choose AWS CDK Over Terraform" medium.com/engineers-haven/i…
Stepping away from a problem can be the best way to solve it... Late last night -> stuck on AoC day 14 for wayyy to long -> eventually decide that sleep is necessary.
Wake up -> open vim -> notice a bug on one line -> fix bug -> solve problem. 🤦♂️
What I learned from AoC today? A dumbo octopus exists. youtube.com/watch?v=eih-VSaS…
Too lazy to even check array bounds on the _first_ AoC problem..
Just placing this at top of the "sliding window" function.. :-)
```
defer func() { recover() }()
```
AoC is definitely not the place for production code 😄
I worry about the bf2042 devs having a bad time with this release full of bugs.
In an industry where “crunch time” is pretty much normalized and w/ pressure from stakeholders, that just can’t be good for mental well-being.
