772 karma · joined August 18, 2014
Many teams don't invest in the tooling required to measure this kind of impact, but it's possible to ballpark it.
USB-C isn’t there yet.
Satoshi is a common name in Japan. I work with a guy by that name and know several others. This says more about your own bias than it does about the title.
Contest unjust fines.
I’ve received 4 parking fines in my life, all were for parking somewhere that had no signage or had signage that permitted my behaviour.
All 4 were successfully contested with photo evidence and a minimum of fuss.
There aren’t any general OKRs or KPIs for software engineers (or most roles in a business) because there’s no business where the raw work product of an individual is an indicator or result in and of itself, barring maybe primary or secondary production industry.
The business has objectives and the individuals in the business work towards achieving them.
Key results depend entirely upon the objectives of the business.
As far as KPIs go, a SWE in a 10-man startup might be evaluated based on getting the damn MVP out the door, while the same SWE in a 100-man startup may be evaluated based on the automation they implement which increases the speed at which their 20-person team can ship.
OKRs and KPIs are tools you can use as a manager to focus and direct the efforts of your team in the right direction. They’re not really an evaluation tool in and of themselves.
There wasn’t anything unusual about my CPU behavior when this happened, I can only assume it was GPU or some other part of the system (unfortunately I was too busy to do more than basic troubleshooting at the time.)
Custom user labels can be arbitrary, non-namespaced free text using any string except “gmail”.
Many (poor) product managers look at velocity dropping and blame the team, or try to pack sprints. In fact, this is the time to open dialogue with the team and get to the bottom of why.
Often, it’s because tech debt or poor architecture is making it difficult to implement even simple features. The team might be burning out. There might be an overwhelming number of bugs and support tickets that need to be addressed.
Story points aren’t a target to hit, or even a KPI. They’re a barometer for team and process health. Unfortunately most engineering and product managers either don’t get it, or are unable to appropriately communicate that fact upwards.
Under normal operation, yes, a lot of information is available there however all pilot training is underpinned by learning to fly the plane by eye, without relying on avionics. Mainly due to the fact that they can and do fail in new and exciting ways.
Even a plane's interpretation of its own configuration can be incorrect, resulting in automated systems believing a given control plane is oriented a certain way, when the reality is very different.
I challenge you to find a mechanism that works for this and is quick enough to keep up at rush hour in the average Tokyo train station.
Additionally, people move at different speeds through the station due to factors like age, familiarity with the network, disability, bladder capacity etc.
It’s a non-trivial problem to solve, and likely only marginally improves user experience.
I'm an expat, living abroad, with a large group of expat friends. Everyone is doing the same thing - thinking about what resources we have access to relative to our families and friends back home, and wondering what we can send them and they can send us.
1. The service is a leaky abstraction, it knows about HTTP status codes and presumably the response body format. The point of separating concerns is to make code reusable, HTTP response codes don't make sense outside of a HTTP call. Similarly, any calling code needs to know that `sortRule` is expecting a MongoDB sort parameter.
2. The control flow is super unclear due to mixing async/await and Promise API coding styles. The `.catch()` call on the promise chain means that the `catch` block will never be hit and the API will always return OK, with the error object exposed to the client in the `responseData` - likely exposing implementation details about the server via the stacktrace on the error object.
There are other nits I could pick, but those are the most important issues and my other criticisms are more a matter of preference.