earlier replies
Replying to @jogbert
you only have a few hours left before it is the wrong year πŸ˜€
2
It’s all about the challenge and learning :-)
1
What language did you pick? I did this year in Rust again to re-teach me about it :-)
1
Go, because we already use a lot of it at work and it makes writing tests easy. Trying to force myself into doing TDD
1
Nice. Makes sense to enhance your Golang experience, and TDD is a discipline I'd love to have myself but have never quite managed to force myself into it.
1
I lost out on a job partly because in the coding tests I didn’t use TDD :-/
1
Interesting. There's a lot of pro's to TDD but also potentially a lot of con's (my boss dislikes its tendency to generate more rigid internal structures since it (in his mind) over-encourages unit testing, not that it has to)
1
Having been a pure sysadmin for a long time, starting to do more β€œdevops” type work and thus more coding has left me rather confused about certain best practices
1
AIUI, the Golang community is pretty strong, so there should be lots of useful/helpful content out there to help you. Sadly I'm almost entirely ignorant of Go (by choice) so I can't help :/
1
Well I meant dev practices in general, not just with Go :-)
1
Replying to @jogbert
Fair, though the best practices vary by implementation domain (e.g. devops vs. appsdev vs. librarydev) and across various axes (e.g. F/LOSS vs. proprietary-internal vs. proprietary-for-others) though if you're lucky then you always use F/LOSS libdev rules :-)

Dec 31, 2017 Β· 10:31 AM UTC

1
Replying to @dsilverstone
And now you start to understand my confusion :-)