There’s a point beyond which no individual, no team, and no company can solve the dependency and constraint puzzle using brute-force methods.
Imagine a company where 10% of the work involves multiple teams, touches different codebases, requires careful coordination, and requires frequent meetings that span organizational boundaries and challenge local incentives. This situation might still be feasible.
Now imagine that this percentage is more like 25%. Very quickly, the constraint satisfaction problem becomes an order of magnitude more complex.
What might a heuristic approach look like in product development?
Reducing work-in-progress limits
Force ranking priorities
Weighted-shortest-job-first
There (is) a chance that teams will miss an opportunity to find an optimal solution? Yes. But the probability of that happening is far outweighed by the likelihood that 1) bad things will NOT happen, and 2) good things may emerge.
The trouble, I believe, is that it can be incredibly hard for managers to make the case for, on the surface, doing less. Discussions about WIP limits and prioritization often devolve into debates over the actual WIP limit and precise estimates! Instead of seeing the forest through the trees, we obsess about finding the optimal answer.
On Twitter yesterday, @RJoads asked me how I got good at styling (CSS).
I replied: “Raw hours. I’m obsessed with how things look and feel—probably more than the median engineer. Mind you, this has not always been a positive. I’ve been wildly distracted for hours and hours on the smallest items, things that truly do not matter to the business. But that’s how I’ve gotten better.”
If you want to get really good at something, forget about shortcuts. You simply have to inject a ton of raw hours.
“Work smarter, not harder” is a common refrain these days—particularly in sophisticated circles. The thing is, for most people I think it’s bad advice. My experience learning to code has suggested you have to work hard before you know how to work smart. No substitute for raw hours.
It’s similar to what Brian Armstrong says: “If you’re pre-product/market fit, the best advice that I have from that period is: action produces information. Just keep doing stuff.”
People with limited experience are similar to startups pre-product/market fit. Of course you should aim to work smarter! The catch is that you have to work extremely hard in order to know HOW to work smart. You must first go down dozens of dead-end paths to know where the smarter paths lie.
The second catch is that in order to be able to inject a ton of raw hours in a natural, sustainable way, oftentimes you need to be OBSESSED. Otherwise – you’ll be banging your head against the wall year after year. Some people are so dogged they’re able to do it. But this is exceedingly rare and probably not worth aspiring to.
“It’s hard to do a really good job on anything you don’t think about in the shower.” – Paul Graham
The power output of a light source is measured using the unit of watts W. This is a direct measure to calculate how much power the light is going to drain from your socket and it is not relatable to the light brightness itself.
The amount of energy emitted from it per second. That energy comes out in a form of photons which we can crudely represent with rays of light coming out of the source. The higher the power the more rays emitted from the source in a unit of time.
Not all energy emitted is visible to the human eye, so we often rely on photometric measurements, which takes in account the sensitivity of human eye to different wavelenghts
“The Color Rendering Index is a measurement of how faithfully a light source reveals the colors of whatever it illuminates, it describes the ability of a light source to reveal the color of an object, as compared to the color a natural light source would provide. The highest possible CRI is 100. A CRI of 100 generally refers to a perfect black body, like a tungsten light source or the sun. ”
