natefinch

7 ms·

31.
by natefinch 7y ago
I mean, you can get a Tesla Model 3 long range for $47k that goes 310 miles on a charge and gains 200 miles on a half hour recharge at a supercharger. That seems... like more driving than I'd really ever do. (half hour is super easy
32.
by natefinch 7y ago
Literally the first non-trivial code I wrote in go (running a bunch of goroutines to download a ton of files from a website in parallel)... I knew exactly where and how things could fail and where things were failing just by looking at the
33.
by natefinch 8y ago
I've been writing Go for over 6 years. Error handling at the source of failure is a feature, not a bug. Rob Pike's example code is bad and I would not allow it through a code review. Why? It makes the code lie. It appears as thoug
34.
by natefinch 8y ago
IF you have a 500k LOC software project... how the heck is an SRE/devops person going to figure out where in that code a specific configuration item is going to be used? They're not. This is why documentation is essential for pro
35.
by natefinch 8y ago
Hugely disagree. Config files will modified by non-experts of the application 1000x as often as the actual developer of the application. Those people won't and often can't go look at the code. Also, it can be really hard to find
36.
by natefinch 9y ago
hell no. Rule #1 - users should never see stack traces. Every time some python tool fails and dumps a stack trace, I want to throw my computer across the room. As as user, I never want to see a stack trace. I have zero interest in de
37.
by natefinch 9y ago
Have you tried micro? It has basically all of that.
38.
3.5 Years, 500k Lines of Go(npf.io)
326 points by natefinch 10y ago|238 comments
39.
by natefinch 10y ago
If you don't know by 21 that calling a woman a milf is degrading and offensive, you're never going to learn. Or at least not in any timeframe where it's valid for this company.
40.
by natefinch 11y ago
Not so bad. And the one I'm working on in Go is definitely helped by being in a simpler language. I don't really think immutable data would be a huge boon to maintainability. Some sure, but I think it would also complicate some o
41.
by natefinch 11y ago
All of the most popular languages have mutable data by default. 99.99% of all enormous systems were written with mutable by default languages. The type system not being "strong" simply means that you put logic in functions and me
42.
by natefinch 11y ago
The Go language is an excellent tool for shipping maintainable server-side applications.
43.
by natefinch 11y ago
The Google name surely gets a lot of people's attention. But if the language actually sucked, it's not going to matter. This is a tool that you have to use EVERY DAY. The Google name is far from a guaranteed hit maker. See Goog
44.
Simplicity and collaboration(dave.cheney.net)
9 points by natefinch 12y ago|1 comments
45.
by natefinch 13y ago
I have a laptop backpack like that. On Monday it was 27ºF at 6:30am when I left for work, but it was supposed to be 55-ish during the day. So, I wore a light jacket under my warmer jacket. My work laptop is a 15" Dell and is somewhat heavy.
46.
by natefinch 14y ago
I never said large. Small proprietary companies also can't use GPL. I guess, fuck them, too? Fuck anyone who wants to actually make money writing software for a living? How very 1998 of you. Doh, I did say large. Well, crap. How about "tho
47.
by natefinch 14y ago
I think it's pretty obvious this is a 5 year old article. And in fact, it has ideas that are much more appropriate to 10 years ago than today. GPL is a hindrance to your code, not a help... unless you're lucky enough to have your code becom
48.
by natefinch 14y ago
This is very good advice. You may not be maintaining your script later on, maybe someone who is new to unix will be asked to go change it. Having the intention much more obvious will save them some hassle. Hell, even someone who uses unix a