Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mr-wendel
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
18 ms
·
151.
▲
by
mr-wendel
6y ago
I'll bite! A rockstar #2. You may be an amazingly gifted, passionately driven, and have a killer idea. Maybe you're mediocre all around. Either way, nothing will improve your chances of success better than having someone you can d
152.
▲
by
mr-wendel
6y ago
A little late on the response, but... People want to know a specific behavior of a system. How often does X happen? What kind of things can trigger Y? Maybe there is documentation, but even if there is nobody trusts it. If folks could just
153.
▲
by
mr-wendel
6y ago
I must disagree with almost everything. > Reality is subjective and so should philosophy be. There is no reason to believe reality is subjective. If it was, why would you appeal to a shared, objective reality to convince us otherwise?
154.
▲
by
mr-wendel
6y ago
I like it too, but I think it misses something crucial: how often is the team unblocking others? This, naturally, is at odds with minimizing interruptions. On one extreme there is no shield around engineers and they experience constant wh
155.
▲
by
mr-wendel
6y ago
Meanwhile, there are reasonable arguments that to at-risk individuals (the youth in particular) making things like this illegal is a near-certain way to draw their attention to it and make it even more exciting. It's not a perfect comp
156.
▲
by
mr-wendel
6y ago
I'd love to no end if there is a major emphasis on the "rehab" part so the incentives AND disincentives are aligned. Less money flowing? Less need for remediation. More money flowing? More need for remediation. More money tha
157.
▲
by
mr-wendel
6y ago
Yes, and no. Power will always be needed, as it represents a differential between knowledge and control over resources. For example, I wouldn't want kids to grow up without benevolent parents! There are obviously other societal layers
158.
▲
by
mr-wendel
6y ago
I'm going to argue no. I wish I could find the HN commentator who said what I've long thought better than I ever could... it was on a cryptocurrency thread, naturally. Such a thing will always have some kind of "emissions&quo
159.
▲
by
mr-wendel
6y ago
Great point. Also, you may have things talking to external resources that are sensitive to timeouts ... even small ones. You may not be able to cleanly resume execution and cause an entirely new problem.
160.
▲
by
mr-wendel
6y ago
This is why every major project I work on has a ".archive/oneshot/" folder for anything complicated that was used to quickly put out a fire. Not only will I inevitably need to remember months later what happened, but I&#
161.
▲
by
mr-wendel
6y ago
Jesus and Satan are having a programming contest to decide who gets to be God's right-hand man. The time limit is one day to create an Earth simulator. They begin, and both furiously code away without taking any breaks. Near the end of
162.
▲
by
mr-wendel
6y ago
Want to learn vim and make it stick? 0. Learn the basic movements and UI interactions. Do NOT use the arrow keys. Your future self will thank you tremendously. 1. Search DuckDuckGo for "vim cheatsheet" and find one that provides a
163.
▲
by
mr-wendel
6y ago
Eager to check it out when it's able to breath again! In the mean time, I can't recommend https://nightride.fm/ enough. Fun retro/synth UI, great stations, and a MilkDrop visualizer for whatever you've g
164.
▲
by
mr-wendel
6y ago
I think it really depends. * How sensitive are you operations to breakage within the repo? Are there key things you can focus on that you know will give you trouble that can be readily tested with each build? * Are you performing a lot of b
165.
▲
by
mr-wendel
6y ago
Absolutely not. It is hard enough to get developers writing meaningful tests that exercise edge cases to make code hard to break. Far too often they do it because "you should" and "we have a policy". Coverage reports too
166.
▲
by
mr-wendel
6y ago
ctrl + ] Totally worth weening yourself off of hitting esc with that combo. Especially because Apple is ... Apple.
167.
▲
by
mr-wendel
6y ago
The problem with scaling upward is how incredibly soul-rending the job is. At some level you're basically guaranteeing that some number of people are going to be traumatized. Maybe at some point the better strategy is to limit public e
168.
▲
by
mr-wendel
6y ago
My pet theory is they're already here and don't care at all about environmental issues. Planets like this are a dime-a-dozen to them. However, nowhere else in the universe have they come across music like ours. They are madly obse
169.
▲
by
mr-wendel
6y ago
I think it's a trap either way. The flip side can also be just as problematic. Having people sincerely wishing you the best, congratulating you on your initiative and dream-chasing tends makes it feel like you're doing something p
170.
▲
by
mr-wendel
6y ago
My contrarian take: 1) Write out your goals in the form of a personal letter to yourself. Focus on the things you think are making you unhappy, not what you think will make you happy. Read it out loud in private. After that, hide it away fo
171.
▲
by
mr-wendel
6y ago
Consider that there are a lot of highly automated email senders that this will never fly for. From small websites/businesses to large (and especially gargantuan!) are more and more likely to contract out email delivery to a specialized
172.
▲
by
mr-wendel
6y ago
"What even is a good specification, or the Huaqiangbei test" Those three points are pure gold! I'd also add that you don't need to be working on a major project to benefit from standing back to writing it out first. Mu
173.
▲
by
mr-wendel
6y ago
I'm afraid not. The best I can do right now is offer an example outline of what I do. That said, if I'm working with a good project manager my format will differ: I'll focus a lot more on the technical details and leave all o
174.
▲
by
mr-wendel
6y ago
Stuff I'd add that I think is crucial, and all related to one topic: good writing! 1. Learn to write specs Call it an RFC, call it a PRD, call it whatever. Writing out a plan for any project taking around a week or more is always wor
175.
▲
by
mr-wendel
6y ago
Similar situation for me in my 20s. It was my first real industry job and in particular was responsible for leading two people who, technically, were way beyond me and had been actively mentoring me. Lessons I learned in this specific conte
176.
▲
by
mr-wendel
6y ago
Yup, it's definitely one of the things Tailscale does. Not an intro or tutorial, but I've not found a better write-up than on their blog: https://tailscale.com/blog/how-nat-traversal-works/ (personally,
177.
▲
by
mr-wendel
6y ago
My hat off to you, all the same. I hope you find a way to pull it off. What you've already produced is impressive. Cheers for the great response to this and other comments!
178.
▲
by
mr-wendel
6y ago
I've developed, maintained, and extended web platforms that all could benefit from what Pegasus seems to do. These platforms have driven up into the million-per-month range of sales for consumer (and team!) based products. The vast maj