1,181 karma · joined October 3, 2017
meet.hn/city/br-Rio-de-Janeiro
I speak for both you and your employer.
technical@theideaofcoffee.com
If you want to have impact, do less! Have a clear vision above all, be able to articulate it, rally people behind you, micromanagement “founder mode” is just a bandaid over poor fearful, leadership. Sure, micromanage your startup of five people, after that you should have the discretion to hire people to carry out your vision. Otherwise, just get out, you’ll just make your life and everyone else’s less miserable otherwise.
Actually quite a few more than that, but yes.
And ooh, ooh, I can flippantly dismiss a comment by calling back to that infamous comment as well! [0] You're actually posting this as a former VP? Geez dude, lighten up, they're not paying you anymore.
And ok, I'll give some leeway in those numbers looking at the map on the linked page, 35% or so of source traffic is clustered over five countries so that distribution skews and some pops around those source countries are going to be hit harder than others. Still, maybe add an order of magnitude and I'll be a little less dismissive.
Maybe because I've had to work on enough remote consoles without any, or limited, color support where I'm more concerned about the problem at hand than which shade of blue is being output for directories. Ok, I'll admit I adjust the default apple terminal 'pro' scheme colors a bit, adding a bit of contrast to the background because I'm in it all day, but beyond that, nothing. I find coloring has little to no positive effect on my productivity, and in some instances, hinders it. No colors on ls, I actually get a bit annoyed when color escapes reach stdout via logs now, hah. Hell, that extends even to my $PS1. I've never bothered to update it on this system. Crotchety, grizzled ops person perspective maybe?
Like some other commenters, things like this were formative in helping me get interested and get really good at electronic-y things. Visits to the store, browsing parts, seeing how things were made and put together were just jet fuel for project ideas.
Someone gets called in the middle of the night? Let them take the morning to recover, no questions asked, better yet, the entire day if it was a particularly hairy issue. This is the time where your mettle as a manager is really tested against your higher-ups. If your people are putting in unscheduled time, you better be ready to cough up something in return.
Figure out what's commonly coming up and root cause those issues so they can finally be put to bed (and your on-call can go back to bed, hah).
Everyone that touches a system gets put on call for that same system. That creates an incentive to make it resilient so they don't have to be roused and so there's less us-vs-them and throwing issues over the wall.
Beyond that, if someone is on call, that's all they should be doing. No deep feature work, they really should be focusing on alerts, what's causing them, how to minimize, triaging and then retro-ing so they're always being pared down.
Lean on your alerting system to tell you the big things: when, why, how often, all that. The idea is you should understand exactly what is happening and why, you can't do much to fix anything if you don't know the why.
Look at your documentation. Can someone that is perhaps less than familiar with a given system easily start to debug things, or do they need to learn the entire thing before they can start fixing? Make sure your documentation is up to date, write runbooks for common issues (better yet, do some sort of automation work to fix those, computers are good at logic like that!), give enough context that being bleary eyed at 3:30am isn't that much of a hindrance. Minimize the chances of having to call in a system's expert to help debug. Everyone should be contributing there (see my fourth line above).
Make sure you are keeping an eye on workload too. You may need to think about increasing the number of people on your team if actual feature work isn't getting done because you're busy fighting fires.
It’s standard training, at least with my NAUI knowledge to practice rescue breathing with another divers spider. My instructor added a few curveballs in that he’d mess up my tank, make me take it off and fix it while without a mask with my eyes closed and breathing off a fellow student’s tank. Nothing to it.
Edit: ok I see you mean as the reporter ostensibly not having any dive training, yeah, probably a bit inadvisable, but they dove with someone with experience and only at shallow depths, the danger is probably a bit overblown after a short amount of instruction. You’re not gonna get bent at 15 ft.
I made a comment a few days ago about how I despair when I see anything modern datacenter related. I get the same sort of revulsion when I look at the list of all of the gpon hardware on that page and thing: how much duplicated and wasted effort has gone in to making dozens of different models of the exact same thing. A thing that's not really even needed if a halfway-competent ISP made an investment that's more than the absolute minimum required.
Nice directory democratizing some good reverse engineering, though!
</end soapbox>
$ python3 -m http.server
I love the connection-specific functions and related structs and arrays for your connection bookkeeping, as well as the poll fd arrays. It's very reminiscent of how it's done in lots of other open source packages known for high throughput numbers, like nginx, redis, memcached.
Great work!
And yeah, I also can't agree more with your assessment about status reports being this relic from the past. What is this? The military? "SITREP. NOW!" Such a waste of breath, time, human life.