Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
acroback
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
acroback
8y ago
Oh yes, we were asked to write positive reviews on Glassdoor. Guess heat I did? :)
32.
▲
by
acroback
8y ago
People get laid off all the time. Business is not hostage to your performance. In the end we all are just numbers of the XL sheet. Treat your company just like one. All the talk about mission reeks of naivety. Seriously, I can understand th
33.
▲
by
acroback
8y ago
As someone who went through this couple of months ago. 1. Code by writing utilities to help your engineers. 2. Never code something which is critical for the release, you will end up blocking everyone. 3. Let engineers make mistakes( which
34.
▲
by
acroback
8y ago
Get some SSDs
35.
▲
by
acroback
8y ago
You give me hope.
36.
▲
by
acroback
8y ago
I have been putting off a Google interview for a whole year now. I have real experience building Cluster Filesystems, Distributed Caches, TCP/IP Control plane software and low latency Ad platform for more than a decade. Sounds good on
37.
▲
by
acroback
8y ago
So basically what ZeroMQ does at far better speeds with better latencies and reliability with a fraction of cost and it doesn't crash or stops operation out of nowhere. Why is everything SaaS, when it is fairly easy to use existing pro
38.
▲
by
acroback
8y ago
We uses ZeroMQ on production as part of a message layer which provide very tight and predictable latencies sustaining more than 300K QPS across multiple services and across 3 data centers(GCP, AWS and private Datacenter). This is a stellar
39.
▲
by
acroback
8y ago
TDD need to die. This is a curse. There should be integration tests along with some property based tests and fuzzy tests. Usually catches a lot of things.Invest in monitoring and alerts too. TDD is like relying on debugger to solve your pro
40.
▲
by
acroback
8y ago
Half of the times it just sits there blank. Sometimes it loads in 2-3 seconds. Rest of the times it loads within 1 sec. Rarely, it also shows a default ad( I work in same industry, hence the term). How is that great? PS: Not talking about n
41.
▲
by
acroback
8y ago
How is this monstrosity going to understand that it is not just practice which makes humans good at team work in Dota2? AI has long ways to go before it can defeat humans in a complex game like Dota2.
42.
▲
by
acroback
8y ago
Start with writing Unit tests for basic functionality. Do not do the cardinal sin of writing unit test for every goddamn function in the codebase like a rookie. Start fixing code, one by one only if it can be tested by Unit tests. Remember
43.
▲
by
acroback
8y ago
I see a disturbing trend in industry especially in Bay area from my experience. Young engineers are bad at debugging, bad means real bad but good at programming puzzles. This points to the fact that people value puzzles over experience and
44.
▲
by
acroback
8y ago
New functionality, breaking existing perfectly fine and working functionality is a big no. One of our core services is written in C, it never crashes, it sustains QPS no other service can in the entire ecosystem, why change it to something
45.
▲
by
acroback
8y ago
I think I did not present this correctly, I apologize for that. What I mean this this. Any IDL interfaces live at their functional boundaries. e.g all proto definitions shared internally by java services live under jumanji/proto/,
46.
▲
by
acroback
8y ago
No, we do not want to pay extra to run Java services bloating our measly VMs. Also, we found that it is far easier to get consistent latency with Go code than with Java code. Again, YMMV benchmark for your use case. That said, Java doesn&#x
47.
▲
by
acroback
8y ago
This means either your contract agreement between services is not language agonistic or someone did not do their job when Interface schema was changed during reviews. Just like any other software, interfaces live in separate repos e.g proto
48.
▲
by
acroback
8y ago
Haha, I made that up to gain free internet points ;)
49.
▲
by
acroback
8y ago
Totally technical considerations which engineers must present and justify. e.g When we added Go, we had to present what it brings? A good testing framework, light weight(subjective), goroutines(which fit our use case), in built benchmark su
50.
▲
by
acroback
8y ago
This is a classic case of not understanding micro services and trying to fit a problem around a tool. At work, we have close to ~50 services(no one calls them microservices), but they do not suffer from this brittleness. We segregate our se
51.
▲
by
acroback
9y ago
Why the f k do these stupid companies then ask really hard Algorithm puzzles in interviews? This is insane, what is imp? Giving too much info or not, asking more questions or not? Oh man, sometimes I hate this process of interviewing.
52.
▲
by
acroback
9y ago
I agree with you. I work for a Startup in valley, and I agree. Our founder CEO was fired recently. Why, you may ask? Because he was a really poor Manager, so poor that even Senior Engineers could see it clearly. Luckily board came to senses
53.
▲
by
acroback
10y ago
I think people are misinterpreting support for try catch family in some high level languages as lazy approaches. But truth is it is the programmers who are lazy, we should not blame language for providing a feature which some programmer abu