1
A career ending mistake
As software engineers, we're constantly making detailed, elaborate plans for computers to execute. Isn't it weird that we rarely give a moment's thought to the program for our own careers?
John Arundel
Friendly, professional Go & Rust training
- Popular posts
- 9
- Total points
- 2,500
- HN comments
- 1,344
- Rank
- #619 personal
Visit bitfieldconsulting.com → RSS feedOn Hacker News Aug 2021 – Nov 2024
Software Engineering 7Career & Management 5Tools & Productivity 2Programming Languages 2Life, Learning & Writing 1Infrastructure & DevOps 1
2
A career-ending mistake
As software engineers, we're constantly making detailed, elaborate plans for computers to execute. Isn't it weird that we rarely give a moment's thought to the program for our own careers?
3
If you need the money, don't take the job
Money: how to get people to give it to you, how much to ask for, and how to be worth what you're asking. Some real talk about the challenges you’ll face as a newly independent worker.
4
Scripting with Go
The Unix shell is pure wizardry. Why shouldn’t it be as easy to write systems programs in Go as it is in the shell? The script library is the secret spell-book that makes this possible.
5
Executable Examples in Go
Did you know that Go lets us provide executable code examples as part of our documentation? It’s pretty neat. Let’s take a tour of this useful feature and see how it works.
6
Constraints in Go
Freedom is nothing without constraints, and Go’s generics gives us a powerful way to build polymorphic types and functions constrained by type sets . Let’s geek out.
7
Fundamentals of Incident Management
When his phone wakes him at two in the morning, operations engineer Andy Pearson knows it’s bad news. The next sixteen minutes are going to get intense.
8
Don't write clean code, write CRISP code
“Clean code” is so over: all the cool kids are switching to CRISP code . I’ll show you how to achieve it in five catchy, T-shirt-friendly slogans.
9
Iterators in Go: A proposed extension
Iterators in Go are a neat way to write “lazy loops”, where we never generate more results than we actually use. Let’s see what that would look like in Go programs, and what new facilities it gives us in the standard library.