Wrote a blog post about how I learned to use monte carlo simulations, and histogram charts to help me estimate and project things like costs, or project delivery dates ... while still communicating the uncertainty of the thing. I'd love to get any feedback or thoughts on this :)
Ever worked with a "Cowboy Coder"? Or perhaps, you yourself are that gun-slingin' cowpoke! What works in a smaller team or startup, can eventually become a liability as a team grows if not managed correctly.
Does your team "move fast and break things"? Or do you slow down and find/fix the root cause every time? As always, the right answer is the classic "it depends", and each approach comes with its own pros and cons.
This is so friggin' cool!! I was wondering recently why Nintendo doesn't use it's already-existing channels of the on-Switch emulators, to let gamedevs make _new_ games for those platforms. That would be such a cool, nostalgic, and potentially lucrative market!
> Ryan Seacrest (yes the Ryan Seacrest) bankrolled a startup 10 years ago with an almost identical product. (They were sued out of existence by an already dying BlackBerry.)
> You'll never get away with an illegal U-turn ever again because the city will pull footage from peoples' internet-of-crap dashcams and the machine learning algorithms will comb the feeds and send fines directly to your mailbox with basically no human intervention.
