Recent submissions

Comment · 4 years ago
That's exactly what I do, don't mind hanging out once a week if you're up for it
Comment · 4 years ago
Comment · 5 years ago
Why not share the seed of the map? This in combination with the coordinates visible on screen would make it possible to check if there is cheating involved. It would be even better if the seed was generated and handed out by a trusted party. Do all the speed runs live and it would be quite hard to cheat.
Comment · 6 years ago
Although the color of the card is black the official name is Centurion
Comment · 6 years ago
You're disappointed with the Silicon Valley bubble, not technology perse
Comment · 8 years ago
Comment · 9 years ago
The Go network stack already makes use of epoll and kqueue: https://golang.org/src/runtime/netpoll_epoll.go So I'm not quiet sure why this would be faster since almost all I/O in Go is event driven, including the networking stack.
Comment · 9 years ago
I think a new Half Life game would be the perfect opportunity for Valve to showcase their virtual reality kit. So far there are no blockbuster VR games and the Half Life franchise (Portal included) has a history of being very innovative (e.g. HL2 using a physics engine for the narrative, HL1&2: story told through level design). There is a lot of potential to use immersive virtual reality to enhance the story telling.
Comment · 9 years ago
Look another product they will retire in about a years time.
Comment · 9 years ago
And don't forget simplicity as a core design feature of the language. That alone is worth sacrificing generics for ;-)
Comment · 9 years ago
Efficiency: I do my thinking/coding/building/writing (not writing emails) in the morning before anyone comes in and can interrupt me. I plan all meetings (which I don't consider proper work) in the afternoons. In short: work first, chatting and socialising afterwards. Some people do like to do it the other way around, which I totally understand and respect. I'm more of a morning person. TDLR; My first 8 hours I start with creating value and at the end of the day I a put in a few extra hours (not always) to socialise ;-)
Comment · 9 years ago
Totally true, I sit at my desk at 7am work till 6pm. The kids come in at 11am and do oh so much over time when working till 7pm. And don't get me started about their relationship problems. And this happy hour is the worst social thing ever. I work in London and there are a lot of people here who don't drink alcohol because of religious reasons or it's not a big part of their culture. Happy hour is only social for people who like to get drunk. No problem with that but a company with a drinking culture will never be diverse and will therefor suffer creatively. I once managed a super multi cultural team (9 nationalities and 5 different religions). We socialised by going to a museum or a historical walk through London. That said, I see a lot of young people who can only can do small talk after a couple of drinks. Which is a shame because it shows when new people join the team.
Comment · 9 years ago
Knowing when to stop is one of the most important things about delivering a project. After trying this method a couple of times I think many will have learned when to draw the line.
Comment · 9 years ago
I do like it when people set themselves challenges like this. Clear beginning and end, finishing something in combination with iterative learning is very satisfying. A bit like a hackaton or a game jam. But this made me think, because in a way it limits yourself in what you can do with what you previously learned. The more you learn the more complex projects you can create and halfway through you can create something which doesn't fit in a day anymore; complexity pushes build time up exponentially. E.g. it needs some extra tooling for generating procedural content. So what I propose is instead of 'over the course of 30 days I will every single day finish a project', why not follow the Fibonacci sequence: I start with nothing (procrastinating), next a one day project, followed by another single day effort. Stepping up with a 2 day project -> a big 3 day project -> 5 day full blown project -> 8 day epic. And finally: a full 13 days working on a single masterpiece! (33 days in total).

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton