throwawaygo

9 ms·

31.
by throwawaygo 5y ago
The v1 guarantee is they will break your code at anytime just like before v1.
32.
by throwawaygo 5y ago
Dude. 5 different ways to handle asynchrony and zero consensus on which is best. A dynamic type system that contains errors like "null is null or not an object". A number system that consists of entirely of floats. Var let const.
33.
by throwawaygo 5y ago
Js optimizes for the wrong thing. Writing code quickly. It's unmaintainable if you walk away from it for a year. Try doing a what you missed in 10 years for go. Lol.
34.
Ask HN: What are the most interesting things in tech lately?
46 points by throwawaygo 6y ago|41 comments
35.
by throwawaygo 6y ago
Yes. Composing archetypal agents in complex adaptive systems is the game I want to see played. Enter into the realm of the structural topology of the brain to see the power of NNs.
36.
by throwawaygo 6y ago
This is some scary shit. Don't use this.
37.
by throwawaygo 6y ago
That said the go team is incredibly talented and deserve a lot of kudos for moving much of the web programming discussion into a simpler understanding of concurrency and type safety. Nodejs and go came out at the same time and node is stil
38.
by throwawaygo 6y ago
The go team's attempt at involving everyone in the priorities of the language has meant they lost focus on the wisdom of the original design. I spent 10 years writing go and I'm now expecting to have to maintain garbage go2 code
39.
by throwawaygo 6y ago
Read code. Every code. All the codes. You are striving to learn strategies for organizing abstraction. Tools are great but your thinking will move faster with a larger vocabulary for organization.
40.
Being Laid Off
39 points by throwawaygo 6y ago|13 comments
41.
by throwawaygo 6y ago
Best thing they could have done. They purchased expertise and a brand that is untarnished and loved in security circles.
42.
by throwawaygo 6y ago
Hard to quantify. Time in language should roughly track. Maybe number of companies/projects developed. Any of the dimensions you could imagine would be good starting points.
43.
by throwawaygo 6y ago
~60% of respondents have <2 years experience with the language. I'd really like to see this filtered to developers with >5 years go experience. What do the experienced go devs want from the language? How do they use it? I'
44.
by throwawaygo 7y ago
Cache rules everything around me.
45.
by throwawaygo 7y ago
This attitude reinforces the the problem. There are lots of jobs that are beneath people or just jobs. People still work them and do them well. Do they need to be excited and open about all their thoughts and feelings too? There's no
46.
by throwawaygo 7y ago
This.
47.
by throwawaygo 7y ago
When did 1:1's become manager interrogation sessions? What happened to just connecting and providing space to talk about whatever is on the emp's mind?
48.
by throwawaygo 7y ago
Yass. This is a really well written go codebase. Go read it and see what life was like before the framework kids showed up.