Notices by muesli (fribbledom@mastodon.social), page 6

I AM GROOT!

3D-printed with Wood PLA.

@aeveltstra

Thanks, that's just the confirmation I was looking for.

Feel asleep on the couch after dinner and - of course - am now wide awake at 2am.

Will I ever learn? 😂

Oh oh, I think 3D printing wood PLA filament is my new favorite hobby.

It smells good, it looks good, it's just rather delightful to work with. Photos later tonight 😊

@jazzyeagle

You can totally get away without a framework. I'd even recommend it to learn how the basic/native http package works.

Most of the frameworks really just provide a bunch of middleware for logging, data validation, caching etc.

According to Cloudflare roughly 18% of HTTPS connections are currently being intercepted (man-in-the-middle):

https://malcolm.cloudflare.com/

Hooray, Deckmaster (a Linux app to control your Elgato Stream Deck) can now trigger DBus calls and emulate keyboard events!

Also, I've moved it into its own repository. Find it here:

https://github.com/muesli/deckmaster/

@philipwhite

A bunch of these fixes could be automated indeed, but I think you'd still always want a human review. Of course you could argue that's the reviewer's or project maintainer's job, but I think it's nicer not to spam them with potentially harmful pull requests.

@CEO

Oh, I love mate! Maybe that's the trick 😂

@KopfKrieg

@KopfKrieg

Love tea, can't stand coffee!

Of course you're right, though, one's energy needs to be carefully managed. It's certainly been a super exhausting endeavor last night and I'll probably need a bit of time to recover this weekend.

Apart from that, the only trick is trying to enjoy what I'm working on. There's a huge difference between having to do something and wanting to do something.

@rgh

Sorry, which one do you mean? I looked at your feed, but I'm not sure I can see it.

@sirspate

*bleep* Oh, no. Must prevent *bleep*

@andrej

Yeah, used a bunch of (static) code analysis tools: goimports, misspell, deadcode, errcheck, govet, ineffassign, staticcheck, structcheck, typecheck, varcheck, bodyclose, dupl, goconst, gosec, unconvert, unparam. To name "just a few" 😂

@314

I wouldn't go as far as saying it's ignorance - or at least that's not what I intended to say 😆

Yes, it can be difficult to find the right set of tools, but on the upside: it's just so difficult to pick and choose because there really are quite a bunch of useful helpers operating on #golang's AST. I really wish we were in that situation for other languages, too.

Check out golangci-lint, btw.

@Matthieu

Posts like yours are the medals I collect 😆

GitHub has given up on catching up with me 😂

"19 repositories not shown"

@amdg2

Yeah, it'd be a lot more challenging and time intensive. Just think of all those compile / build cycles 😂

Other things I've learned tonight:

- all those context switches between dozens of projects are a lot more exhausting and mentally draining than you could possibly imagine

- this would have been a lot worse without #golang's strict coding style and formatting conventions

- many projects have a CI pipeline set up, but ignore lots of the brilliant code analysis tools the Go ecosystem provides

- Maybe C++ projects next? Not sure that's a good idea for my mental health 😂

Tried identifying the most common #golang mistakes and went on a little bug hunting mission tonight:

Fixed hundreds of bugs & issues across 39 of the most popular Go projects, and created more than 100 pull requests. 28 of which have already been merged in the past couple of hours!

Here's what I most commonly encountered:

- typos
- unnecessary conversions
- ineffectual assignments
- tautological errors
- missing error handling

Here's the full list: https://github.com/pulls?q=is%3Apr+author%3Amuesli (login required)

@thurloat

Prints in one go, no assembly required!