9 ms·
In this thread: mostly people responding to the headline, not the actual content of the article. There's some fantastic stuff in here about how great design is
by simonw 10y ago
In this thread: mostly people responding to the headline, not the actual content of the article.
There's some fantastic stuff in here about how great design is the key to increased productivity. For example:
"It is very important for a designer to recognize all the parts of a design that are not easy wins, that is, there is no proportionality between the effort and the advantages. A project that is executed in order to maximize the output, is going to focus exactly on the aspects that matter and that can be implemented in a reasonable amount of time. For example when designing Disque, a message broker, at some point I realized that by providing just best-effort ordering for the messages, all the other aspects of the project could be substantially improved: availability, query language and clients interaction, simplicity and performances."
redis itself is a masterpiece of pragmatic design - the feature set is brilliantly selected to make the most of what you can do with shared data structures exposed over a network. Let's talk about that.
- acqq 10y agoExactly. All the arguments that have the word "productivity" are probably off. It's not about "productivity" as in "which programmer produces more code" or even "more programs" or whatever. It's about the person being able to recognize what matters, on one side, versus those that can even make such decisions to finally cause the doom of the project. I have such experiences, and some huge failures can really be caused by the disconnection on the lower levels (programmers) and the managers who can't recognize what's going on (accepting the wrong arguments of these doom-causing programmers). Some of stories like that are also in the book "In Search Of Stupidity" http://www.insearchofstupidity.com/ http://www.insearchofstupidity.com/ The author calls them "marketing disasters" but I recognized several purely technical disastrous decisions there, like "let's rewrite the product from scratch, but ignore the way the users use the product (to print) and ignore the printer drivers existing in the earlier version." Then wonder why nobody wants to use the new version, and the competition takes over. These things are eternal in tech. On another side, if we claim that as soon somebody is making any design decisions is not "just a programmer" then sure, all the programmers are "good enough." The way I understand it, antirez probably considers himself a programmer and for what he produced he really made most of the design decisions himself? But if you factor in the design decisions: they can make the product great or kill it. What's the difference then between the best and the worst? Much more than 10 times, if we compare the survival vs. the death, it's even infinite.
- simonh 10y agoMy favourite programming anecdote[0]. How many lines of code did you produce today? -2000. Indeed it's not about lines of code. A 10x programmer might produce a solution that would take a team of three 1x programmers twice as long to implement and is twice as 'good' (fast, compact, stable, elegant, maintainable, etc). It's interesting that this anecdote is from Apple, as Steve Jobs was a famous proponent of the 10x or 20x programmer and hiring only the best available. In contrast at Microsoft Charles Simonyi took completely the opposite approach, with a highly stratified organizational structure dependent on hiring large numbers of drone programmers[1] and reducing programming tasks down to easily implementable essentially rote modules. I don't think it's a matter of one model or the other 'winning' though as the Simonyi strategy certainly seemed to work for MS. [0] http://www.folklore.org/StoryView.py?story=Negative_2000_Lines_Of_Code.txt http://www.folklore.org/StoryView.py?story=Negative_2000_Lin... [1] https://en.wikipedia.org/wiki/Charles_Simonyi#Denmark_and_USA https://en.wikipedia.org/wiki/Charles_Simonyi#Denmark_and_US...
- acqq 10y agoThanks for a hint! Reading [1], there the "programmer actually making decisions" was called a "metaprogrammer": "the metaprogrammer was the designer, decision maker, and communication controller in a software development group.... individual progammers were allowed to make no design decisions about the project. All they did was write the code as described by the metaprogrammer." In that case, the differences between programmers can't be too big and surely matter little. It's the "metaprogrammers" that are important and influence the faith of the project. And those that Jobs praised were, by that definition, surely "metaprogrammers" who also did the tasks of "programmers."
- simonh 10y agoThe meta programmer model is very different though. How the programmers implement their code is not addressed. Fast? Compact? Memory efficient? Maintainable? Doesn't matter, perhaps as long as the code meets some pre-determined criteria.
- dtornabene 10y agohad a similar response. lots and lots in this piece that actually works out as fairly profound advice.
- Spooky23 10y agoIn defense of those people, the layout of the site is actively hostile to people on mobile. -10x for readability.
- antirez 10y agoI'm sorry, for the kind of things I tend to blog about, monospace font was the simplest way to have a truly what-I-write-is-what-appears without using any markup. If I could start from scratch I would use MarkDown, however at this point if I switch all the past blog posts will be broken, or I should switch conditionally from a post ID >= but then the blog will be a bit inconsistent. I'll try to figure out a solution.
- sn9 10y agoDan Luu's website is an example of a blog with extremely simple markup that's very readable on mobile and desktop.
- KirinDave 10y agoYou could make it so new posts have markdown, but your old ones are untouched? Honestly, your site is probably the very hard to read, but some of the problems it has are just omissions on your part If you want to see how to make monospaced fonts readable in bulk, pattern your layouts after phrack.
- antirez 10y agoGreat, I'll check the Phrack site. Thanks!
- RangerScience 10y agoI'm on a phablet and it was easy to read. (Also liked it and have questions)
- zokier 10y agoAs a quick fix, would changing width: 800px to max-width: 800px for #content help in CSS?
- LoSboccacc 10y agoone million time this. as the resident tech lead I spend more time trying to get people focus on things that matters than actually designing and documenting can provide daily anectodes but here's the last one: we use a javascript scrolling library, for reasons etc, long story short a programmer spent a couple day trying to figure out why the horizontal bar wronly showed on edge, until I went in and dropped a display none on the bar itself. ultimately we aren't paid for technical excellence but for working programs.
- cabalamat 10y ago> we use a javascript scrolling library, for reasons etc, long story short a programmer spent a couple day trying to figure out why the horizontal bar wronly showed on edge, until I went in and dropped a display none on the bar itself. Wouldn't an even simpler solution be to just use the scrolling built into browsers?
- victormustar 10y agoI'll do r&d for 1 or 2 days and give you the right answer :)
- unoti 10y agoIf you need smooth scroll you can't rely on browser support and need to use a library or cook something up yourself. It's surprising how few browsers work with smooth scroll. Today it's basically only Firefox; not even Chrome.
- woah 10y agoNot to be a fanboy but I use a Mac and one of the things that they clearly did a huge amount of research and fine tuning on is the scrolling. I can always tell when there's non native scrolling on a site and it always sucks. Maybe I'm out of touch, but IMO the smoothness of the scrolling is an OS or hardware level feature. If somebody's OS or hardware does not scroll smoothly, then clearly it's something that they're used to from every other site they visit. Putting a "smooth scrolling" library in makes about as much sense as rendering all of your site's text on canvas because some computers have font aliasing issues. It reeks of a micromanaging CEO getting fixated on some arbitrary requirement that makes stuff look better only on his computer.
- endorphone 10y agoIn this thread: mostly people responding to the headline, not the actual content of the article. And the headline was purposefully chosen to elicit that effect -- nothing engenders a massing crowd response quite like summoning the boogeyman of the 10x programmer, allowing everyone to flow forward with their anecdotes and personal grievances.
- colomon 10y agoAnother great thing here: "Design sacrifice: killing 5% to get 90%." I remember a very specific example of this from Perl 6 development circa 2009. perlgeek (I think) and I had been struggling with coding up the sequence operator for a couple of months. Every time we thought we had it, someone would come up with a case that broke the system again. pmichaud (not sure if it's the same pmichaud here on HN) comes up to us and says something like, "Guys, you're not getting this, let me do it." And I was kind of offended, because it wasn't like perlgeek and I were chopped liver; why did he think he could easily solve a problem that had been plaguing us? But here's what pmichaud did. He went up to TimToady (Larry Wall) and said, "There's too much magic in the sequence operator. We need to simplify it." I don't know which combination of the two of them came up with the details, but less than 24 hours later the spec had been changed so that there was no magic on the right hand side of the operator and they had a working implementation. Any sequence possible before was still possible, but the user was required to be more specific about what they wanted. After the change the median sequence took maybe two more characters to specify ... but suddenly 90% of the hard part of coding the operator was gone.
- snarf21 10y agoPerfect is the enemy of good enough. If you never ship a "perfect" product, it has 0 value. In the end, you provide value or you don't. The hardest thing about any product development is to stop taking things out or worse yet, keep adding things in. The top performers are usually the ones who can weigh these pros and cons almost immediately and force the product in a better direction.
- MichailP 10y agoAnd good enough is the enemy of at all. Love this little piece of wisdom from Paul Buchheit.
- atmosx 10y agoI had a similar experience while trying to devise an algorithm to fill up n spots having n-1 soldiers available in the military. So after losing few hours, not being able to come up with any combination that satisfied all conditions I run to the sergeant, explained the problem and he just erased a spot for 24h, changing spec. Suddenly everything fell in to place. Alexander the Great did the same thing in order to solve the Gordian Knot[1], he changed the spec by removing the complexity (in one stroke). I was not in a position to even think about proposing the removal of any spot that had to be guarded at all times. Doing so, might have resulted in someone (including myself) doing double-shifts for a few days. Only he who has the power can do it (e.g. Larry Wall for Perl, Alexander the Great for the Gordian Knot and the sergeant for the military camp). [1] https://www.wikiwand.com/en/Gordian_Knot https://www.wikiwand.com/en/Gordian_Knot
- jerf 10y ago"great design is the key to increased productivity" Given how many times the 90/10 principle will brutally murder your time estimates ("we're 90% done, so there's only 90% left to go!"), learning to also harness it in your favor as antirez talks about is a great programmer differentiator. If 90% of the effort is coming from 10% of the design, and you can find some way to cut that part of the design in half, you just cut 45% of your effort out. My numbers are made up, but the principle holds. Most of the time you don't get that lucky, but every once in a while it is possible to do even better; I have, on occasion, seen entire seemingly-massive multi-month projects dissolve into 200 lines of code in the right place, built on the right foundation.
- DougWebb 10y agoI'm proud to say that I've accomplished that, at least once. My company was developing a new feature, hundreds of medical textbooks that would be searchable and readable online. The source content for each textbook consisted of a huge xml file and a bunch of images. The problem we faced was that many of our customers were government-funded libraries, and they required a physical product for anything they purchased. (We wanted to sell renewable access licenses for the online product.) We were discussing this in a meeting with the C-level execs and other top employees, and they were working out a plan for bulk manufacture of CDs containing the textbook content. Many of the textbooks already had CDs that came with them when you bought the physical book, but most of them did not, and we'd need to manufacture copies in either case. There was liner material to produce, CDs and cases to buy, global distribution to manage, and a new department and headcount needed to manage all of this. I interjected with an idea. I was building the online display of this content, and had already built everything needed for converting the xml into a table of contents display and per-chapter displays, all in html with the styling that we wanted, including features like the substantial amount of cross-linking between sections, chapters, figures, indexes, appendices, etc. So I told them "You know, as part of the production process where I'm converting all of this xml for online display, I can also produce a set of static files that would work well for an offline display, either sitting in a folder or on a CD. We can do that, create an iso image from it, and let the customers download the iso and burn their own CD if they want physical possession. It'd be exactly the same content, and would only lack the online searching and dynamic excerpting features that the website has which depend on our search engine." They were stunned. They discussed, and decided that for most of the customers this would be just fine, and for the handful of exceptions we could burn the CD for them and mail it. We included a cover-art image from the book on the CD if they wanted a liner, and our download links had a little help icon that pointed to documentation we wrote for a few free CD burning utilities. Overall cost was a few extra days of development time.
- brightball 10y agoThis was an excellent read. There are people who are great a design. There are people who are great at architecture. There are far fewer people who are great and making the tradeoffs needed to sacrifice part of a design or part of a "perfect" architecture when they aren't necessary to a project. You've really got to have people who have a culture of celebrating trimming the fat at both ends to get to that.
- zeteo 10y ago> In this thread: mostly people responding to the headline, not the actual content of the article Agreed - the actual content reads more like "The mythical 10x programmer ... is me". ("many people told me that they believe I’m a very fast programmer... I’ll also use myself as a reference of coding things fast"). I don't mean to disparage Redis or the author, but the point needs to be made that seniority makes it a lot easier to be a "10x" programmer. First off, you have excellent knowledge of business requirements and PMs will listen to you; so it's relatively easy to redefine engineering tasks as you work on them ("killing 5% to get 90%"). Second, you're much less likely to be interrupted by someone who's decided you're working on a low-priority project ("focus"). Third, you probably get to decide what "programmer productivity" even means.
- neutralid 10y ago> It is very important for a designer to recognize all the parts of a design that are not easy wins, that is, there is no proportionality between the effort and the advantages. In optimization, if you make an analogy between speedup / improvement with advantages / effort, you get Amdahl's Law: https://en.wikipedia.org/wiki/Amdahl's_law https://en.wikipedia.org/wiki/Amdahl's_law "[T]heoretical speedup of the execution of the whole task increases with the improvement of the resources of the system and that regardless of the magnitude of the improvement, the theoretical speedup is always limited by the part of the task that cannot benefit from the improvement."
- odbol_ 10y agoSo you're allowed to name laws after basic common sense now?
- amelius 10y agoAnother good example of simple design is Slack. They completely eliminate the sharding problem by allowing each user to be in at most one team.
- Debugreality 10y agoGreat article, as I'm a bit of an old hat myself I'd like to add a few extra categories - Knows how to handle not knowing or getting stuck - some people have a melt down or won't ask for help when they hit a wall or don't know when to push back (we had a vendor that gave us buggy code but kept claiming it wasn't until we pushed back through our management and forced them to let us see the code). Can visualise the program - how much of a program someone can hold in their head is the only thing I've really seen make a programmer exceptional. It is rare and I've only met a couple of people that can hold a medium sized program in their head, the whole thing this ability lets them basically just vomit it all out into the editor without having to switch between functional and structural context and really does make for a big productivity bonus (maybe as much as 4x).
- lacampbell 10y agoIs that really a long-term productivity boost? I wager the cost of maintaining and debugging the vomited code destroys any total productivity advantage. Of course I am completely biased in that I can bold barely anything of a program in my head. I feel like that makes me a better programmer in terms of writing shorter, maintainable code. It's hard to assess yourself honestly though.
- Debugreality 10y agoIt's true the resulting code isn't perfect. But there are design advantages to holding the code in your head that make up for sloppiness at least that was my observation. A code review for error checking is certainly advisable and good practice to boot!
- lacampbell 10y agobut the thing is the poor person finding bugs or adding features in the code is going to spend 2x as long. and then 2x as long the next time, and the next time... "no we can't re-write it, it's working code! just add the feature...". If Mr. 4x had slowed down a bit and written something more structured, the overall cost would have been less, surely.
- mstade 10y ago> Let's talk about that. Sorry, doesn't fit in a two week sprint.