christophberger

6 ms·

1.
by christophberger 2y ago
The first rule of writing safety-critical systems in C: Don't write safety-critical systems in C.
2.
by christophberger 3y ago
You don't need to measure your impact. It's enough to describe it. "Helped a large client improving their web presence for achieving increased conversion rates." Of course, you were part of a team and of course, you can&
3.
by christophberger 3y ago
A must-read (or rather: must-see) for anyone who thinks exponential backoff is overrated.
4.
by christophberger 3y ago
The number of lines needed is not a good measure for gnarliness. (To be fair, I don't know if gnarliness is measurable at all.)
5.
by christophberger 9y ago
I am afraid I cannot give you a direct answer, but here are two thoughts: 1. There seem to be a consent among Gophers to avoid frameworks where possible and use libraries instead. Frameworks are good for a quick start but when you hit their
6.
by christophberger 9y ago
I wonder how the current Go 1.9.x compares to v1.7.3 that was used in the article (which BTW will become one year old tomorrow - happy Birthday!)
7.
by christophberger 9y ago
Author here. I am excited to announce my Go course for devs who have little or no knowledge of Go and want to learn the complete language from scratch. Happy to answer any questions. (But expect delays, it is end of day over here)
8.
Course: Master Go – Go from Scratch for Developers(appliedgo.com)
2 points by christophberger 9y ago|1 comments
9.
by christophberger 9y ago
This may be an interesting article; however, I stopped reading when I discovered that it is about math/rand and not crypt/rand. Any PRNG that is not cryptographically secure must be flawed by definition (otherwise it would qualif
10.
by christophberger 9y ago
> is that a valid hypothesis ? No, unless you have some solid studies at hand that would clearly support your „hypothesis“, it is nothing more than a highly biased imputation. Here is my antithesis: Elixir/Erlang doesn‘t sustain for
11.
by christophberger 9y ago
The readme might deserve some love. A one-liner is not that helpful... :)
12.
Show HN: Control a Digispark with a few lines of Golang code(appliedgo.net)
1 points by christophberger 9y ago|0 comments
13.
Know Big-O before applying performance optimizations to your Go code (golang)(appliedgo.net)
1 points by christophberger 9y ago|0 comments
14.
by christophberger 9y ago
Generics have their use cases, but in general they are overrated. Especially in (but not limited to) the DevOps area, I bet that 99% of the code needs no generics at all. Having said that, I would not complain if the concept of Ply ( https:
15.
by christophberger 9y ago
> which makes it possible to change the path of project without worrying about GOPATH Trying to ignore GOPATH, or trying to work around the requirements of GOPATH, often calls for trouble.
16.
by christophberger 10y ago
Go is a pragmatic language, designed for programmer productivity. I think Go was never meant to be used as a language for reasoning about models and concepts at various abstraction levels and for arbitrary problem domains. There are certain
17.
by christophberger 10y ago
Argh! Forgot to include the "golang" keyword :)
18.
Text-Based User Interfaces in Go – Beef up your commandline tools(appliedgo.net)
20 points by christophberger 10y ago|4 comments
19.
by christophberger 10y ago
Swift and Go aren't competitors. Different realms, different audiences.
20.
by christophberger 10y ago
This Reddit thread reveals why the algorithm works: https://www.reddit.com/r/golang/comments/5xrjh0/got_lucky_im...
21.
by christophberger 10y ago
You are absolutely right to ask about possible downsides of a language before deciding to make the switch. However, there is a problem with your question: Define "not great". Every programming language has - and lacks - specific f
22.
by christophberger 10y ago
IMHO the term "idiomatic" is overused. Every programming language has its idioms, and I am sure you'll learn them when working through Go tutorials, books, or courses. Important here: Empty your teacup if you want to fill in
23.
by christophberger 10y ago
If you want to contribute to the Go project itself, this article is a good start: https://blog.gopheracademy.com/advent-2016/contributing-to-t... For all other Go projects, check the project documentation or ask the ma
24.
by christophberger 10y ago
Depends on the situation.
25.
by christophberger 10y ago
You could use a Go "project" that is in fact the $GOPATH, like so: |-- projects |-- project_0 |-- project_1 |-- project_2 |-- go |-- src |-- pkg