Thats where I would have to make decisions, and deciding correctly takes time.įirst off, it's a bit unfair to me that you were the one to make this comment, since your very extensive experience and deep knowledge of real-time systems makes you uniquely qualified to disprove my point!! heheīut in all seriousness, I agree with most of what you said - I think I'm just more bearish on people's ability to infer those many decision points without being given the blueprint like we were in this article. And hence, thats where the scope might blowout for me. So I'd need to learn the right way to implement it. I rule out doing the mobile notifications not because I think it would be hard, but because I haven't done it before. Programming without needing to learn is just typing and typing is fast.
In a sense, I think programming is slow and unpredictable because of the learning we need to constantly do.
Etc.)īut I couldn't implement r/place that quickly if reddit didn't already do all the work deciding on the scope of the problem, and what the end result should look like. Tie the versions into a rendered image URL and use nginx to cache. Use CQRS, then have caching nodes I could scale out and strong versions using the event stream numbers. The product decisions are specified in the post (image size, performance requirements) and for the technical decisions I can rely on experience.
CRITICAL OPS HACK 1.8.0 FULL
Thats possible not because I'm special, and not because I'm full of it but because most of the hard decisions have already been made. With all that said, I bet I could implement r/place in less than a weekend with the requirements stated at the top of that blog post, so long as I don't need to think about mobile support and notifications. Not all the polish and testing you'd actually need to launch a real product. When people say "I could copy that in a weekend", they're usually only thinking about the core functionality. I'm sure Uber and Facebook have hundreds of little features like that. Check out this 'should we send a notification in slack' flowchart. For most products, most of the actual work is in little features and polish thats 'below the water', and not at all obvious to an outsider. If you have a lot of development experience in a given domain, you don't need to make as many decisions to come up with a good structure - your intuition (tuned by experience) will do the hard work for you. When looking at an existing thing (like r/place), most of the product decisions have already been made. There are three reasons why people feel confident saying "I could copy that in a weekend": Decisions can take the form of a product questions - "what are we making?" and development questions - "how should we implement that?". Whats really going on here is that development time scales linearly with the number of decisions you need to make. the too-common comments on Reddit and HN where people claim that they could rebuild FB or Uber as a side project.
0 kommentar(er)
