reledi

    python -m SimpleHTTPServer 443

OP means you should be raising the bar for hiring at your org.

The problem is when requests for larger ideas and tasks do not go through your PM/PO (they should be protecting their team from "malicious" requests so they can meet their milestones on time).

For example, someone from product or marketing shouldn't be able to walk up to you randomly and request that you build something for them. (When they do, redirect them to your PM/PO.)

Regarding why people apply in the first place. Uber is basically a household name around the world, so they can attract a lot of applicants. There's also little insight into the working conditions and comparisons to competitors. And the sales pitch is very misleading; you're told you receive weekly payments and how much you can expect based on weekly hours, except they don't mention you're quoted a monthly figure unless you clarify.

I much prefer to use code coverage as a weak indicator for finding dead code.

It's good to use hyperbole black and white when teaching so the point comes across easier. But they should be made aware of caveats before they graduate at least.

We should start using the header and avoid guessing, but sites won't use the header unless the data is reliable. The data being reliable is a UX problem that browsers can fix.

This is creative, and if your blog is hosted via GitHub Pages, then using Issues to discuss the content is not far-fetched at all.

You don't even need to use a dependency like Kafka. We built a tool for tracking the lifecycle of software we ship, it uses Event Sourcing with snapshots and is open source: https://tech.fundingcircle.com/blog/2016/09/06/shipping-in-f...

Instead

1. Quickly experiment with refactoring but stop if it feels wrong. We often underestimate how quickly we can improve the codebase. It's often better to try something quickly than waste time planning to do it.

2. Defer if it's a big refactor or you're on a very tight deadline. Write a reminder in your physical notebook so you don't prematurely pollute your board. If it feels high priority after that and you still haven't had time to do it, then make a chore ticket for it.

- HEADLINE: Better support for printers

- DESCRIPTION: I haven't been able to connect to the office printer after many attempts. The driver isn't included with Ubuntu and the generic driver doesn't work. Tried installing specific driver via Canon's website which came with overly difficult instructions and it still didn't work.

- ROLE/AFFILIATION: Software Engineer at a (recently joined) company that's switching from Microsoft to Linux.

The problem is when this behaviour crosses over into your professional life, because you're not delivering value to your customers quickly enough and as a result you'll either get sacked or the company can go bust. Having someone else to keep you in line works great, it doesn't even need to be a Product Manager or Product Owner. And if you don't have someone else to keep you disciplined, then you better work hard on improving this area where you're lacking. Write down ideas on paper for example and ruthlessly prioritise and prune them every morning. Sayings like "work on what's highest priority", "do the least amount of effort that results in the greatest value", "keep it simple", "reduce scope", "you aren't gonna need it", "defer nice to haves", and so on are things we hear so often because it really is good advice that you should follow.

Imagine you're checking if the value is equal to a number or string. Placing the variable on the RHS avoids accidentally assigning a value to it if you mistype the comparison operator.

This is called Yoda conditions: https://en.m.wikipedia.org/wiki/Yoda_conditions

Edit: Many people already commented the same thing. Sorry for the noise!

Would have really appreciated a push notification as soon as the issue occurred -- they sent one a few hours too late.

If you're running a critical service, please make sure you have an appropriate and working notification strategy for major failures.

Is there any way you can verify the authenticity of your story without losing your anonymity to the public? For example, would Susan be able to verify you as an ex-employee?

https://github.com/facebooknuclide/atom-in-orbit#motivation

Also pairing with someone who's more experienced than you.