ubu7737

11 ms·

1.
by ubu7737 5y ago
You can replace a derailleur hanger on a modern bicycle for about $10 or less. This is the part that bends on a right-side crash.
2.
by ubu7737 6y ago
HEAD_TRUNC? Is this to detect when Autopilot has driven through a freight trailer and severed the driver's head?
3.
by ubu7737 6y ago
A beloved co-worker and the best engineer on my team suddenly had to leave 2 months ago because his H1B renewal was denied. He asked the company HR for help and they sent him home immediately. Tears in his eyes he left us on a Thursday, and
4.
by ubu7737 6y ago
My mood disorder has made my whole career a rocky journey. I'm 43 now, and doing well in my current role. Managing your depression will always be part of the trip. Don't listen to the voice(s) that say you are a failure/loser
5.
by ubu7737 7y ago
4k on a 27" screen at desk-sitting distance is worth whatever trouble you've been avoiding. Text is indistinguishable from print type. You're able to see an enormous amount of information without panning. With a good mouse yo
6.
by ubu7737 7y ago
ROFL "performance tuning" this is not tuning this is architecture. Some people think you can just write software, sell it to customers, and it's "tuning" to make it work properly. You should be fired from whatever j
7.
by ubu7737 7y ago
Downvoted for angering the VC class...
8.
by ubu7737 7y ago
> Dramatic rewrites to a codebase Otherwise known as re-architecting?
9.
by ubu7737 7y ago
Where I work compliance is job #1. That doesn't prevent us from thinking about performance. GTFO with this nonsense.
10.
by ubu7737 7y ago
There is simply no excuse for this. You are a software engineer or you are not, the cadence of change is part of the technology aspiration. I have no patience for persons who don't belong to the discipline.
11.
by ubu7737 7y ago
> But it's possible this migration process would have been easier if we had done it sooner. What the f *? Of course it would have been easier if you had done it sooner. What you lacked was the willpower from decision-makers who had
12.
by ubu7737 7y ago
> what's the impact and ROI of a language migration vs getting Node to work as well as we can? Hire an architect costs what? Putting the genie back in the bottle was a problem Plaid baked into its early success, which is common with
13.
by ubu7737 7y ago
Seems pretty easily-fixable, if it's just one byte.
14.
by ubu7737 7y ago
Spring is semi-magical but when you learn the whole thing it gives you godlike abilities.
15.
by ubu7737 7y ago
A level sitting surface won't allow your spine to curve naturally. I don't know why, but most people are not aware of kneeling chairs or the benefits they provide to back posture. There is literally no way to get healthy curvature
16.
by ubu7737 7y ago
Urges won't translate into practice so easily. The abstractions of servers won't be so easily reduced to stateless method calls. The design of a cloud-based service is still so relevant that there is no abstraction which can possi
17.
by ubu7737 7y ago
I completely agree. This "looking for the non-leaky boundaries" approach favors simplicity and reliability. Microservices present huge wins; choreographing them poorly is really on you. Nobody said making the leap to distributed s
18.
by ubu7737 7y ago
I agree with you, but I want to add some precision to this. In some meetings I feel powerless, and I find them absolutely horrible. In other meetings I have a voice anytime I want to use it, and I feel powerful, and I wouldn't miss the
19.
by ubu7737 7y ago
Google lost its varnish around the time it sought to fight Facebook with Plus. Around the time they released the Nexus 7. I guess around the time Sundar became ascendant.
20.
by ubu7737 7y ago
When I used PG for my job queue, I was already using Kafka instead, to handle immediate job entries. The reason I needed PG was for jobs scheduled at a future time . I had no difficulty with long-running jobs because servicing jobs out of
21.
by ubu7737 7y ago
Right, I was working mostly off one very well-written article on the topic, it was an easy search because there is really only one correct way to implement atomic job-handling with PG.
22.
by ubu7737 7y ago
It makes the job-fetching more atomic, as the article points out properly. If you take >1, you have to sort the situation where 1 or more jobs fail, which adds an unreasonable amount of complexity. On my first go I was taking batches, on
23.
by ubu7737 7y ago
The main reason to dig down is to uncover faults and leaks in abstractions, which is something you absolutely will have to do in the fullness of time. A corollary reason is to improve your "mechanical sympathy" when writing high
24.
by ubu7737 7y ago
Used the "FOR UPDATE SKIP LOCKED LIMIT 1" trick to implement a job server in PG a few years ago for the first time. It's a great solution.
25.
by ubu7737 7y ago
On my new XPS 13 4k, text is wonderful everywhere.
26.
by ubu7737 7y ago
> Where I get weary I think you mean either "wary" or "leery" but not both at the same time!
27.
by ubu7737 7y ago
Nobody writes C# except for the sake of fitting into the .NET ecosystem. Java is the original dorky reference-oriented language with underlying bytecode, and after 20 years of runtime optimization it's still the best. Newbies of every
28.
by ubu7737 7y ago
It really feels as though someone has done career JVM professionals a huge favor, sending all the upcomers to Python and PHP and Golang. Let them learn in their sandboxes, right? Newcomers don't need connectors anyway, they need the ro
29.
by ubu7737 7y ago
It's a great reason to write a new runtime. JVM is still okay. If you thought using a new language would give you better runtime character, you were wrong. Languages are transpiled and cross-compiled on the reg, and it really makes no
30.
by ubu7737 7y ago
Sorry. I was actually goofing on the fact that Go demos are rehashing the history of C. And frustrated that I'm not hearing anything from Golang programmers about how it enables a larger class of software. "We're writing the

More ›