News for hackers. Stuff that matters.
Re:Qualities that I believe make the most difference in prog... by simonw on Tuesday February 28, 2017 @07:33AM (#13753278)
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.

Re:Qualities that I believe make the most difference in prog... by colomon on Tuesday February 28, 2017 @09:23AM (#13753894)
Another 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.

Re:Qualities that I believe make the most difference in prog... by atmosx on Tuesday February 28, 2017 @11:05AM (#13754722)
I 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

Re:Qualities that I believe make the most difference in prog... by rak00n on Thursday March 02, 2017 @02:39AM (#13772322)
I think you'll like George Pólya's How To Solve It. That's one of the methods he prescribed on solving a difficult problem; by gently removing the most difficult part and look at it again.
Re:Qualities that I believe make the most difference in prog... by gav on Tuesday February 28, 2017 @03:49PM (#13757663)
Finding a better solution by changing the problem is great, especially as the problem stated is often not the problem faced.

Not doing something, or doing something dramatically simpler, ends up with less code being written. The cost of writing the code is usually a small fraction of the cost of supporting it during over the life span of the system.

One problem I faced was a client that as part of an e-commerce re-implementation brought a huge list of requirements for promotions and how they should work. There was hundreds of use-cases, some being very complicated.

I came back to the client and said, "are you sure you need all of this?" After working with them to investigate, it turned out that they had just documented all the features of their existing system. In the previous ten years, they had created exactly one coupon, and that was for a flat 10% off.

That was the functionality we initially went live with.

Re:Qualities that I believe make the most difference in prog... by jakobegger on Tuesday February 28, 2017 @05:11PM (#13758630)
This is the difference between a real programmer and a coding monkey.

Coding monkeys consider the spec the problem and try to write code that solves it.

Programmers consider the spec a part of the solution and evolve it as necessary.

Re:Qualities that I believe make the most difference in prog... by bigiain on Tuesday February 28, 2017 @06:27PM (#13759303)
Interestingly this is pretty much "valuing individuals, working software, and customer interaction" - the core of the agile manifesto, but the bits that never seem to ever show up in "Agile" workplaces where way too often rigid compliance with standups, scrum meetings, and evenly sloped burndown charts (and foosball table, bean bags, and free energy drinks) are all "critical to the process", and fixed price engagements and hard deadlines are "the business reality"...
Re:Qualities that I believe make the most difference in prog... by taneq on Tuesday February 28, 2017 @09:01PM (#13760287)
"The problem is not the problem, the problem is your attitude towards the problem." - Jack Sparrow

So many times I've seen someone struggle to implement a poorly written spec rather than just say 'hey can we just do X instead?' If X solves the REAL problem then sure you can.

Re:Qualities that I believe make the most difference in prog... by hex13 on Wednesday March 01, 2017 @06:33AM (#13762956)
> the problem stated is often not the problem faced.

100% true! So many times I was assigned to the task in issue tracker, where requirements was written, estimation was made, but after I sat and tried to solve given problem, it turned out that 80% of issue description was false - real problem was totally different than it was written in task.

What seemed right on planning meeting, turned out to be quite false in the process.

But quite often managers/product owners etc. don't understand this. They often believe 100% in planning ahead and issue tracker/backlog descriptions... And when something is going off the track (like it sometimes does - when problem needs extra time for thinking through) they aren't so glad because thinking and design process was not budgeted in issue tracker (even if it could lead to the better design on the long run).

Re:Qualities that I believe make the most difference in prog... by snarf21 on Tuesday February 28, 2017 @10:41AM (#13754498)
Perfect 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.

Re:Qualities that I believe make the most difference in prog... by MichailP on Tuesday February 28, 2017 @06:46PM (#13759450)
And good enough is the enemy of at all. Love this little piece of wisdom from Paul Buchheit.
Re:Qualities that I believe make the most difference in prog... by ram_rar on Tuesday February 28, 2017 @02:15PM (#13756837)
I wish somebody writes a book accumulating such stories. Nothing excites me more than learning from history.
Re:Qualities that I believe make the most difference in prog... by andrey_utkin on Tuesday February 28, 2017 @03:29PM (#13757545)
Check "The Art of Unix Programming" by Eric Raymond. It's full of exciting stories from computing pioneers epoch, and more than that, it's just filled with empowering inspiration about simplicity. To quote just one story from this book:

> One epochal example not mentioned in Gabriel's paper is from distributed hypertext systems. Early distributed-hypertext projects such as NLS and Xanadu were severely constrained by the MIT-philosophy assumption that dangling links were an unacceptable breakdown in the user interface; this constrained the systems to either browsing only a controlled, closed set of documents (such as on a single CD-ROM) or implementing various increasingly elaborate replication, caching, and indexing methods in an attempt to prevent documents from randomly disappearing. Tim Berners-Lee cut through this Gordian knot by punting the problem in classic New Jersey style. The simplicity of implementation he bought by allowing “404: Not Found” as a response was what made the World Wide Web lightweight enough to propagate and succeed.

Re:Qualities that I believe make the most difference in prog... by trumbitta2 on Tuesday February 28, 2017 @05:21PM (#13758720)
Kobayashi Maru
Re:Qualities that I believe make the most difference in prog... by jerf on Tuesday February 28, 2017 @09:26AM (#13753918)
"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.

Re:Qualities that I believe make the most difference in prog... by DougWebb on Tuesday February 28, 2017 @10:26AM (#13754370)
I'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.

Re:Qualities that I believe make the most difference in prog... by fastbeef on Tuesday February 28, 2017 @12:19PM (#13755416)
I hope you were handsomely rewarded for saving the company tens of thousands of dollars, if not more.
Re:Qualities that I believe make the most difference in prog... by DougWebb on Tuesday February 28, 2017 @02:49PM (#13757189)
Hundreds of thousands, probably, and my work on that textbook feature brought in millions in revenue. Another aspect of the project is that I wrote a custom XML content storage and retrieval database, and spending a couple of months proving that my solution was far more scalable and performant than either the Oracle-based solution or commercial XML database solution that the director of development and CTO preferred. So I saved the company a 6-7 figure annual licensing cost as well.

My reward was short-lived immunity to the corrosive political environment that the CTO and director of development had created. The director came from a competitor we had acquired for their customers (not their tech), and right from the start he was open about wanting to eliminate our development team so that his old team could be in charge. They failed due to incompetence, and he and his entire team were let go some years later. The CTO lasted longer, eventually firing my manager without cause, and I quit a few months later. The overall product we were responsible for (which the textbooks were a part of) is still running, and it is still their flagship. But very little has been done to it in the past seven years since I left. The CTO was let go a year or two after I left.

Handsomely rewarded? Hardly. That's not how it goes in big corps. Presiding over the hand-off from the team that was let go was satisfying, and knowing that my software is still running strong after many years of neglect because everyone who was capable of maintaining it quit is also somewhat rewarding.

Re:Qualities that I believe make the most difference in prog... by bigiain on Tuesday February 28, 2017 @06:33PM (#13759342)
Heh - did pretty much the same thing (not for medical textbooks) but included a title/keyword/first few hundred works text search thing as a Java applet, for this "Best viewed with Netscape 3!" was actually relevant! ;-)
Re:Qualities that I believe make the most difference in prog... by edblarney on Tuesday February 28, 2017 @12:04PM (#13755229)
Great story.

That's exactly it.

Re:Qualities that I believe make the most difference in prog... by SatvikBeri on Tuesday February 28, 2017 @08:02PM (#13759964)
At one of my first jobs, my employer had $1.2MM and 10 people budgeted full time for 2 years to build a project that would allow managers to make queries on a very large dataset.

I pored through the specs, talked to everyone who would use this, and realized all the queries could be calculated from a much smaller, summarized version of the data.

I wrote a script that would create an Excel PivotTable every month and send it to everyone who asked, solving the problem in a few weeks with a <500 lines of code. The execs decided it would not be worth spending an extra two years to get the exact same answers in a web UI.

Good times.

Re:Qualities that I believe make the most difference in prog... by brokenmachine on Friday March 03, 2017 @12:15AM (#13780910)
It's amazing how much time and money one intelligent person with ideas can save a company if their ideas are actually able to be implemented.

I hope you ended up seeing some of that $1.2M, yet somehow I doubt it.

Re:Qualities that I believe make the most difference in prog... by Debugreality on Tuesday February 28, 2017 @04:53PM (#13758387)
Great 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).

Re:Qualities that I believe make the most difference in prog... by lacampbell on Tuesday February 28, 2017 @08:03PM (#13759979)
Is 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.

Re:Qualities that I believe make the most difference in prog... by collinmanderson on Wednesday March 01, 2017 @09:27PM (#13770898)
"vomit" maybe isn't the best word.

The point is they are able to in their head: compose the program, notice bugs, fix those bugs, possibly tweaking the design in the process.

Basically, they can prefect the design in their head and fix a lot of bugs all before starting type.

Re:Qualities that I believe make the most difference in prog... by Debugreality on Tuesday February 28, 2017 @08:33PM (#13760147)
It'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!
Re:Qualities that I believe make the most difference in prog... by lacampbell on Tuesday February 28, 2017 @10:02PM (#13760607)
but 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.

Re:Qualities that I believe make the most difference in prog... by Debugreality on Tuesday February 28, 2017 @11:43PM (#13761193)
No nothing like that at least the couple I've worked with. I think you are confusing these people with "coding minds" with people that can churn out working code quickly (they are a different beast). The code produced by the 4x people is very elegant structurally because they can see how it fits together, this is the strength but it may be missing some edge cases / functionality and or validation in the first pass.
Re:Qualities that I believe make the most difference in prog... by jdmichal on Wednesday March 01, 2017 @12:10PM (#13765668)
That second addition is not nearly as valuable for creating code as it is debugging it. When you see an error and can pretty much pinpoint where the problem is, just because that's the only place where that error makes sense... That's a lot of time you just cut out of the entire process.
Re:Qualities that I believe make the most difference in prog... by acqq on Tuesday February 28, 2017 @07:56AM (#13753375)
Exactly. 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/

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.

Re:Qualities that I believe make the most difference in prog... by simonh on Tuesday February 28, 2017 @08:10AM (#13753447)
My 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_Lin...

[1] https://en.wikipedia.org/wiki/Charles_Simonyi#Denmark_and_US...

Re:Qualities that I believe make the most difference in prog... by acqq on Tuesday February 28, 2017 @08:18AM (#13753489)
Thanks 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."

Re:Qualities that I believe make the most difference in prog... by simonh on Tuesday February 28, 2017 @09:55AM (#13754112)
The 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.
Re:Qualities that I believe make the most difference in prog... by acqq on Tuesday February 28, 2017 @10:24AM (#13754353)
In the metaprogrammer model, as far as I understand, the programmers don't even decide "how the programmers implement their code," that's what the metaprogrammer decides: if what they produced is acceptable and according to his exact instructions or is to be rejected. So they don't decide: "Fast? Compact? Memory efficient? Maintainable?" they do it exactly the way the metaprogrammer said.

What I wanted to point is that as soon as we define that the programmer doesn't decide, we have a system where the "quality" of the programmer doesn't matter much as the programmers by that definition do more-or-less a mechanical task.

However that "metaprogrammer" term is probably not so common. How are metaprogrammers called otherwise? What are their job titles?

Re:Qualities that I believe make the most difference in prog... by unoti on Tuesday February 28, 2017 @11:47AM (#13755063)
> However that "metaprogrammer" term is probably not so common. How are metaprogrammers called otherwise? What are their job titles?

In places that use this approach the people filling that role are sometimes called Architects, Principal Engineers, and sometimes Product Managers or Technical Product Managers.

Re:Qualities that I believe make the most difference in prog... by brightball on Tuesday February 28, 2017 @10:09AM (#13754239)
This 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.

Re:Qualities that I believe make the most difference in prog... by LoSboccacc on Tuesday February 28, 2017 @09:02AM (#13753777)
one 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.

Re:Qualities that I believe make the most difference in prog... by fredsir on Tuesday February 28, 2017 @09:44AM (#13754037)
> 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.

If that is something that has to be done a couple of times in a projects whole life, fine. If that is how bugs are solved all the time or frequently, I can only imagine how bad the codebase will be to maintain in years, and how depressing a job it must be to work on it.

That line of thought bleeds that no-one cares about the project, and only cares that the "people paying for it" hopefully don't notice the state of affairs underneath, and that they are not in a position to switch away from the product when ultimately it burns, which it will, if that is how bugs are treated. It bleeds that money is the only incentive, not heart, not passion, and that's just sad. It's why so much software is so bad and ends up costing much more in the long run than fixing the damn bugs properly right now, either because you end up having to maintain it until death, because it's so hard to maintain, or because you can't keep increasing customers after years because the product is now in such a bad state that time is spend fixing/hiding bugs instead of adding new features or improving existing ones.

> ultimately we aren't paid for technical excellence but for working programs.

That is true for most people and most projects, unfortunately. Bugs should not be covered and hidden away, they should be fixed.

Re:Qualities that I believe make the most difference in prog... by TimJYoung on Tuesday February 28, 2017 @10:47AM (#13754557)
I had the same reaction as you to this post, so thank you for nicely summarizing my thoughts.

I'll just add:

To me, the main distinction is this: you must at the very least figure out the reason for the unwanted behavior. If you don't, then you really have no idea whether your quick little fix covered up something important or not.

It's one thing to investigate, find out the cause, and then say "meh, that's way too expensive/time-consuming to fix, so we'll switch libraries/3rd party code or just remove the requirement for the special scrolling". It's quite another to just say "meh, display: none, look at how productive I am !".

I've had other developers do this in front of me, and it freaks me out to no end. One sat there and told me that if he changes a month calculation to subtract a month, then the total comes out correctly. I asked him why that was and he said "Why does it matter, I'm getting the right result ?"

We all need to remember that we're not being paid to type, we're being paid to think.

Re:Qualities that I believe make the most difference in prog... by BurningFrog on Tuesday February 28, 2017 @11:01AM (#13754683)
Re:Qualities that I believe make the most difference in prog... by TimJYoung on Tuesday February 28, 2017 @11:46AM (#13755059)
Beautiful, thank you.
Re:Qualities that I believe make the most difference in prog... by sbov on Tuesday February 28, 2017 @12:58PM (#13755863)
Re:Qualities that I believe make the most difference in prog... by LoSboccacc on Tuesday February 28, 2017 @01:05PM (#13755973)
In a third party library which already touches a sensitive area that shouldn't messed with in the first place? That'd be a week of two of work, easy. Means reaching a client less. No way I'm gonna chase the white rabbit in its hole to fix something that has no side effects and zero ripercussion on other components.
Re:Qualities that I believe make the most difference in prog... by cabalamat on Tuesday February 28, 2017 @09:10AM (#13753834)
> 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?

Re:Qualities that I believe make the most difference in prog... by avereveard on Tuesday February 28, 2017 @01:02PM (#13755907)
Because while default scroll is fine for scrolling pages whole, in any scrollable div that's not top level it looks out of place like a blacksmith on an iceberg.

It's a gray slab that looks like a tombstone riding a straight, dull rollercoaster and unless your site makes a point of having a '90s inspirational look there's no way to integrate them in a page so that it doesn't feel completely detached.

Re:Qualities that I believe make the most difference in prog... by lacampbell on Tuesday February 28, 2017 @08:06PM (#13760001)
If I was in your team I would be saying "why not just scrap scrollable divs?".

I am always looking for excuses to get rid of stuff.

Re:Qualities that I believe make the most difference in prog... by victormustar on Tuesday February 28, 2017 @09:15AM (#13753858)
I'll do r&d for 1 or 2 days and give you the right answer :)
Re:Qualities that I believe make the most difference in prog... by unoti on Tuesday February 28, 2017 @11:34AM (#13754952)
If 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.
Re:Qualities that I believe make the most difference in prog... by woah on Tuesday February 28, 2017 @12:16PM (#13755383)
Not 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.

Re:Qualities that I believe make the most difference in prog... by unoti on Wednesday March 01, 2017 @12:02AM (#13761307)
I'm not talking about manually implementing a virtual scrollable canvas. I'm talking about "make item 19 in that list box visible in the middle of It's display area."

I agree that scrolling virtual spaces should be native and hardware accelerated whenever possible, but I think we are talking about different use cases.

Re:Qualities that I believe make the most difference in prog... by collinmanderson on Wednesday March 01, 2017 @09:33PM (#13770927)
document.querySelector('.item-19').scrollIntoView()
Re:Qualities that I believe make the most difference in prog... by T-hawk on Tuesday February 28, 2017 @02:53PM (#13757233)
What web page or application would need smooth scrolling? What can't work with whatever scrolling is normal for the browser/OS/hardware?

Looking cool at the request of some manager does not constitute a need.

Re:Qualities that I believe make the most difference in prog... by unoti on Tuesday February 28, 2017 @11:46PM (#13761211)
Imagine there's a scrollable list of items and you want to scroll one particular item into view when some event happens. Without smooth scroll the item just pops into view and the user may not see it happening. It's a usability issue-- when the user interface jerks instantly, the user can lose context about what's happening. When it's smoothly animated it's easier for the user to keep track of what's happening in the user interface, and to see how one interaction triggers the next.

Done right, animation isn't just snazzy, it produces a more usable, more approachable user interface. It helps the user keep a good mental model of what's going on. It's easier for them to mentally track "ah, when I select this item, it also selects that other item in the other list".

It's the same reason why when you click an app on your phone it animates up from the app icon when the window opens. The animation wordlessly tells the user "I'm opening this app, and the window that's appearing is born of the icon you just clicked." Necessary? Not exactly. More natural? Absolutely. Nothing just snaps into existence in the real world, except for maybe things like lightning.

When things appear out of nowhere it can be jarring. Animation is especially called for when it might not be intuitive why you're making a change to the visual state, or when you want to call attention to something.

Keep in mind that a generation ago, pretty much every piece of software (even games!) came with a printed manual that the user needed to read first before expecting to be able to accomplish anything. Today users expect to be able to figure things out for themselves, and animation is part of the user experience that helps users learn their applications naturally by exploring the user interface.

Re:Qualities that I believe make the most difference in prog... by K0SM0S on Wednesday March 01, 2017 @08:12AM (#13763393)
Exactly, and just we wait for mainstream VR/AR. I believe we'll see quite a lot of animation skeumorphism (is that a thing? I mean realistic animation/appearance relatively to a real world setting, e.g. gravity on objects, diffraction on transparency, etc). For a few years at least, time for users to learn new interaction paradigms and positioning within a virtual/hybrid environment.
Re:Qualities that I believe make the most difference in prog... by bigmanwalter on Tuesday February 28, 2017 @06:04PM (#13759111)
This is what I use right now for cross-browser smooth scrolling. It's native first with a jQuery fallback.

  <style>
      html, body {
          scroll-behavior: smooth;
      }
  </style>

  <script>
      // Uses native smooth scrolling if available, otherwise uses a jQuery fallback
      // Just add data-scroll attribute to any anchor you want to make smooth
      // Add data-scroll-header to a sticky nav / header to offset the window top
      if (!('scrollBehavior' in document.documentElement.style)) {
          // jQuery fallback
          // Taken from https://css-tricks.com/snippets/jquery/smooth-scrolling/
          $('[data-scroll]').click(function() {
              if (location.pathname.replace(/^\//,'') == this.pathname.replace(/^\//,'') && location.hostname == this.hostname) {
                  var target = $(this.hash);
                  target = target.length ? target : $('[name=' + this.hash.slice(1) +']');
                  if (target.length) {
                      $('html, body').animate({
                          scrollTop: target.offset().top - $('[data-scroll-header]').height()
                      }, 600);
                      return false;
                  }
              }
          });
      }
  </script>
Re:Qualities that I believe make the most difference in prog... by cabalamat on Wednesday March 01, 2017 @10:36AM (#13764472)
> If you need smooth scroll

Why would I need smooth scroll? All it achieves is slows down the scrolling so it takes me longer to get to where i want to in the page.

Re:Qualities that I believe make the most difference in prog... by noxToken on Tuesday February 28, 2017 @09:45AM (#13754040)
> ultimately we aren't paid for technical excellence but for working programs

In my very un-expert opinion, there has to be a balance between technical excellence and working program.

I'm assuming that your case is really a non-issue. A dev wanted to find the root cause of the issue, fix the issue, and then never have to worry about it again. That's an admirable quality to me, but from your quick fix, it proved to be too much overhead for so little gain.

On the other hand, you can reach a point such that you peel back a Band-Aid brand adhesive bandage, you find a generic brand adhesive bandage atop a goopy dollop of ointment atop rotting wounds. I think technical excellence is knowing when a quick-fix for your situation is good enough and knowing when you really need to roll back the sleeves to dive in.

Re:Qualities that I believe make the most difference in prog... by KirinDave on Tuesday February 28, 2017 @10:25AM (#13754361)
> ultimately we aren't paid for technical excellence but for working programs.

Depends who you are, now doesn't it? People writing core OS components, network infrastructure, cloud servides, etc have a much higher bar to hold to.

But I'm in agreement with antirez that good design and solid technical underpinnings often make projects go much faster. Even if you don't know it by heart, being able to research the tools you need can give better results than not knowing at all.

Re:Qualities that I believe make the most difference in prog... by amelius on Tuesday February 28, 2017 @12:36PM (#13755583)
It also depends on what you want to do, of course. Job satisfaction matters too.
Re:Qualities that I believe make the most difference in prog... by Teckla on Tuesday February 28, 2017 @12:26PM (#13755491)
ultimately we aren't paid for technical excellence but for working programs.

Some level of technical excellence is required, though, otherwise complex technical debt piles up, and we are then no longer able to deliver working programs.

Re:Qualities that I believe make the most difference in prog... by LoSboccacc on Tuesday February 28, 2017 @12:55PM (#13755805)
Technical debt on something that outer on the stack is irrelevant, there's nothing we need to build on top of this behavior
Re:Qualities that I believe make the most difference in prog... by SpaceManiac on Tuesday February 28, 2017 @02:01PM (#13756666)
Nothing you need to build, but your customers will be building their workflow around your outer layer.
Re:Qualities that I believe make the most difference in prog... by neutralid on Tuesday February 28, 2017 @11:35AM (#13754960)
> 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

"[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."

Re:Qualities that I believe make the most difference in prog... by odbol_ on Tuesday February 28, 2017 @08:25PM (#13760122)
So you're allowed to name laws after basic common sense now?
Re:Qualities that I believe make the most difference in prog... by amelius on Tuesday February 28, 2017 @12:32PM (#13755545)
Another good example of simple design is Slack. They completely eliminate the sharding problem by allowing each user to be in at most one team.
Re:Qualities that I believe make the most difference in prog... by dtornabene on Tuesday February 28, 2017 @07:57AM (#13753387)
had a similar response. lots and lots in this piece that actually works out as fairly profound advice.
Re:Qualities that I believe make the most difference in prog... by mstade on Tuesday February 28, 2017 @05:44PM (#13758948)
> Let's talk about that.

Sorry, doesn't fit in a two week sprint.

Re:Qualities that I believe make the most difference in prog... by zeteo on Tuesday February 28, 2017 @10:36AM (#13754451)
> 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.

Re:Qualities that I believe make the most difference in prog... by endorphone on Tuesday February 28, 2017 @09:05AM (#13753803)
In 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.

Re:Qualities that I believe make the most difference in prog... by Spooky23 on Tuesday February 28, 2017 @09:00AM (#13753766)
In defense of those people, the layout of the site is actively hostile to people on mobile.

-10x for readability.

Re:Qualities that I believe make the most difference in prog... by antirez on Tuesday February 28, 2017 @09:40AM (#13753999)
I'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.
Re:Qualities that I believe make the most difference in prog... by sn9 on Tuesday February 28, 2017 @10:07AM (#13754220)
Dan Luu's website is an example of a blog with extremely simple markup that's very readable on mobile and desktop.
Re:Qualities that I believe make the most difference in prog... by KirinDave on Tuesday February 28, 2017 @10:14AM (#13754264)
You 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.

Re:Qualities that I believe make the most difference in prog... by antirez on Tuesday February 28, 2017 @10:35AM (#13754446)
Great, I'll check the Phrack site. Thanks!
Re:Qualities that I believe make the most difference in prog... by Spooky23 on Tuesday February 28, 2017 @09:13PM (#13760347)
Personally it wasn't the font for me but the way it wraps. I have some annoying vision issues that pop up from time to time. My solution is to use Safari reading mode on iOS, but that made it worse in this case.
Re:Qualities that I believe make the most difference in prog... by zokier on Tuesday February 28, 2017 @12:29PM (#13755516)
As a quick fix, would changing width: 800px to max-width: 800px for #content help in CSS?
Re:Qualities that I believe make the most difference in prog... by RangerScience on Tuesday February 28, 2017 @12:06PM (#13755255)
I'm on a phablet and it was easy to read. (Also liked it and have questions)
Re:Qualities that I believe make the most difference in prog... by KirinDave on Tuesday February 28, 2017 @10:04AM (#13754191)
The site's layout and typography is actively hostile to readers in general, mobile or no. The choice of a monospaced font in spite of all readability, the letter spacing, the lack of headings, list marking or indentation, the extremely wide lines...

It's a design anti-pattern that makes the article difficult to read, even if you don't have a cognitive differences that make reading more challenging.

Re:Qualities that I believe make the most difference in prog... by hfsktr on Tuesday February 28, 2017 @10:08AM (#13754228)
I thought you were exaggerating but you are right. It is hard to read. At least the text is visible (not gray on light gray) so that is a positive.
Re:Qualities that I believe make the most difference in prog... by mundanevoice on Tuesday February 28, 2017 @12:25PM (#13755485)
Not true, I just read it on my 5" Android phone and it was pretty okay to read. I won't call it hostile at least.