Backslasher

5 ms·

31.
by Backslasher 3y ago
I bumped into them when looking arouns. During the interviews you could tell the CTO had a huge backlog of juicy items that had a healthy mix of "things I have a clear idea of how to deliver" and "areas I'd like to learn
32.
by Backslasher 3y ago
I appreciate your feedback. I don't think I'm non-committal, more like afraid of being boxed into a too-small domain. The last sentence is factually incorrect. During my time at FB I contributed code to the container solution, the
33.
by Backslasher 3y ago
I tried doing that, but couldn't land a starting gig with reasonable pay. To my impression, the market is flooded with cheap-to-hire people and I couldn't make my quality stand out enough to get interesting clients. If you have an
34.
We don't do DST at this company(blog.backslasher.net)
6 points by Backslasher 3y ago|1 comments
35.
by Backslasher 3y ago
Most definitely. Most of my time in FB was spent at the very least making FB a better company. I was solving problems that impacted our users or our engineers. The last year though, not so much. I joined a team that I believed was doing rev
36.
by Backslasher 3y ago
While interviewing post-FB to other companies as an SRE-type-engineer, it seemed to me that outside of FANN it's not common to give engineers a very wide scope. One company asked me whether I'd like to join the monitoring team or
37.
Ask HN: Why are there no profiles on Android browsers?
3 points by Backslasher 3y ago|3 comments
38.
Is this really an emergency?(blog.backslasher.net)
3 points by Backslasher 3y ago|0 comments
39.
by Backslasher 4y ago
The brain and the brawn :)
40.
by Backslasher 4y ago
A.S --> E.A, no? :) I decided to abstract away the URL part as it wasn't easily explainable and not important to the story. I figured the JSON-in-JSON part is interesting enough. Anyway, the resulting memdump with many \\s remains m
41.
by Backslasher 4y ago
I do not know why this is a JSON object. It might have been for debuggability, although I don't agree with this choice.
42.
by Backslasher 4y ago
I joined the team long after this was in production, but I can testify that the service has a lot of moving parts and attributing the reliability / efficiency costs for a specific issue was challenging.
43.
by Backslasher 4y ago
We ended up doing that. We decided that while we have to store the stack, it can't hold 20 years of history. > creating a dedicated real stack with self-imposed size limits and reporting.
44.
by Backslasher 4y ago
The real formula we used to order servers was more complex than this, and included regional distribution, requirement peaks etc. I can expand more on that process if this is interesting. However, for the context of this post, this crude app
45.
by Backslasher 4y ago
This is correct :)
46.
by Backslasher 4y ago
Ha, this is a nice coincidence. I was looking for a cool domain name a billion years ago and came up with Backslasher since I was just learning text processing in Bash/Perl. My lifelong goal is beating the same-named horror film in sea
47.
A 1.5GB string(blog.backslasher.net)
308 points by Backslasher 4y ago|138 comments
48.
SelfDecode Assistant job responsibilities: “Organizing dates for CEO”(facebook.com)
1 points by Backslasher 6y ago|0 comments