NateDad

54 ms·

511.
by NateDad 12y ago
Waffle.io looked good, but maybe too simple. I will probably start there and see if there are any missing pieces...
512.
by NateDad 12y ago
Blossom looked pretty good, but wasn't sure about if it might be too feature heavy and cause too much time bring spent on the tool rather than work.
513.
by NateDad 12y ago
Yeah I saw the chrome extension, not really into that.
514.
by NateDad 12y ago
Sorry, was trying to avoid biasing the results. Looked at waffle.io, zenhub, huboard, blossom.io... Some others. Google kanban github and a bunch come up.
515.
Ask HN: What's your favorite GitHub-enabled kanban board?
3 points by NateDad 12y ago|9 comments
516.
by NateDad 12y ago
People can write bad code in any language. I don't know that "forcing" people to know about it will do anything other than force people to make a possibly bad decision... such as simply marking all values as mutable. The nic
517.
by NateDad 12y ago
Suggesting that offshoring is a result of languages that are "too easy" is both insulting to those who work offshore, and totally inaccurate. There's plenty of off-shore C++ programmers, and I doubt anyone would say that&#x2
518.
by NateDad 12y ago
People often ridicule what they don't understand. People who haven't written real code in Go don't understand why it's good. And what makes it good isn't that it has X feature, so it's hard to explain to peop
519.
by NateDad 12y ago
Developers & managers at Stripe decided that Go was being used often enough to spend precious dev time writing an official library which will have to be supported from here on. They wouldn't do that if the numbers didn't just
520.
by NateDad 12y ago
Wow, great link, thanks!
521.
by NateDad 12y ago
Oh, then you'll love Go. It's nothing like python. At least, not like the python you've described above. Go is actually quite different from python in a lot of ways. Most of the stuff you hate about python does not apply t
522.
by NateDad 12y ago
The problem with "languages for those who can" is that they get relegated to pet projects, because real teams need code that everyone can understand, not just the "rock stars". I actually hope that Rust does not become t
523.
by NateDad 12y ago
Any language seems inconsistent and has hard to remember syntax for people who are new to it. Unlike most of other languages, you can learn Go in a weekend and get beyond the newbie problems. There was a great article lately about Go'
524.
by NateDad 12y ago
Gccgo misses out on some key optimizations, like escape analysis IIRC, and therefore on real world tests usually is not as fast as gc. Also, since gc is the de facto standard, it has a LOT more real world testing. Gccgo has a few bugs (I f
525.
by NateDad 12y ago
I find discourse (discourse.org) to be a much better groups replacement than an email list. Email lists are so 1999.
526.
by NateDad 12y ago
Go is a very pleasant language to develop software products in. Unlike the dynamically typed languages, it doesn't trade speed for beauty of syntax. This means that sometimes syntax can be a little non-uniform, but there's always
527.
by NateDad 12y ago
It's 10 lines of very obvious code. Isn't that a good thing? Do you really need stack.New<T>()?
528.
by NateDad 12y ago
Simply embedding the type and writing whatever additional methods you need is actually incredibly easy. The boilerplate beyond what is required to actually define the new functions is really tiny type Foo struct { pkg.Bar
529.
by NateDad 12y ago
I think a lot more bugs are introduced from people trying to make their code too generic rather than too specific. The complexity of the code goes way up when you stop being able to rely on certain values being certain types. If I &quot
530.
by NateDad 12y ago
Um wow no. Go is a language for people who write servers. It is really really good for those uses. Look at Docker, etcd, Kubernetes, Juju, Cloudflare, Soundcloud ... And probably a ton that are internal to a company and not really exposed
531.
by NateDad 12y ago
I wish people wouldn't assume there's only two options - Generics or casting from Object/interface{}/void* It's a straw man argument. No experienced Go programmers are trying to say that's a good way to write
532.
by NateDad 12y ago
It sounds like you were forced to write/maintain some Go code and are basing your opinion on that, an opinion heavily colored by the quality of the original code and your annoyance at your employer for making you work in something othe
533.
by NateDad 12y ago
I write go 40 hours a week and have been for over a year. There's been only a couple times I wanted generics and those are structures I haven't actually needed to reuse yet. I'm not guessing about not being generics much. E
534.
by NateDad 12y ago
You don't have to resort to an empty interface, in fact, mrust experiences go programmers cringe when they see anyone using empty interfaces. The fact of the matter that much code can reused without being "generic" and often
535.
by NateDad 12y ago
The answer is not that you should use an empty interface, the answer is not to write generic functions.
536.
by NateDad 12y ago
I think you have a mistake in your analogy. We're more like mechanical engineers drawing complicated CAD diagrams. It's just that we don't need a whole factory to produce our product, because it's not physical. All we
537.
by NateDad 12y ago
I don't believe that. The speed of producing code is not relative to typing speed. LOC per day depends on the complexity of the lines. I can write 500 simple lines or 50 complex lines of code in a day. I'd agree that higher le
538.
by NateDad 12y ago
Go has gc and gccgo. They made two implementations to keep the spec honest and not just "whatever the compiler does".
539.
by NateDad 12y ago
> Few things scream "name your salary" in this business like being a competent and willing COBOL programmer. Uhh.... if you can find someone looking for a COBOL programmer in your area, perhaps. But the number of COBOL jobs ou
540.
by NateDad 12y ago
In practice this is not a problem that is encountered pretty much ever. If you are afraid of it, run errcheck[1] on your code, and it'll tell you if you've missed anything. [1] https://github.com/kisielk/errc

More ›