23 ms·
I am fed up to the back teeth with "speed" as a positive metric for coding. > used to taking a long time to think about and solve a coding problem. that's a g
by lifeisstillgood 13y ago
I am fed up to the back teeth with "speed" as a positive metric for coding.
> used to taking a long time to think about and solve a coding problem.
that's a good thing. A good friend of mine is a phd and lead programmer on a radio telescope project. my solution to a problem he described was quick to code and hellish to run, his involved maths I did not understand took five lines and ran super fast. he chose an algorithm that fit the problem domain better - because of more extensive training than I got.
Algorithms count massively. Google is built on an algorithm that fits the problem domain better. finding and applying better algorithms to give "unfair" competitive advantage is a very good thing
so I want to see a slow code movement like a slow food movement
- Producing higher quality software delivers more business value in the medium term than lower quality
- Iterating to a solution is often slower than applying the best algorithm directly
- it takes time to understand and evolve a story
- rewrites are a good thing. most books and film scripts are rewritten a lot
- daily status meetings encourage trying to do something each day instead of taking a week to make something fantastic
- jerguismi 13y agoI see no problem here. If algorithms count massively, then those slow skillful algorithm coders can start their own companies, and because algorithms count massively surely soon the market will be full of companies that require algorithmic skills and don't value speedy hacks. But just surprisingly, the market looks like it is full of those crappy startups, which value speed over quality, and don't do rewrites. Wonder why that is so.
- peterkelly 13y agoActually algorithms are kind of important. How do you think it is that google is able to return your search results in a fraction of a second? And how is a game able to represent and efficiently display a massive 3D world?
- jerguismi 13y agoI didn't claim that algorithms are not important. If you look at the market, there is a lot of demand for certain types of employees, while there is less demand for others. I think that the market represents pretty well what people actually demand. The comment I replied to implies that demand is specified by the companies, not by customers. I guess you get that kind of attitude in university jobs, where money comes from goverment grants etc, not from customers.
- gbog 13y agoIt could be that we see many startups in "the market" because like flies they spawn and die quickly, but have few to nil influence on the world, while real big new things are few and last longer, and influence the world, and require higher skill levels. Think about it, between Instagram and Bitcoin, which will be influencing our world and our life more?
- quanticle 13y agoThe problem is that for the vast majority of business applications there is no algorithmic innovation required. I mean, to build a basic CRUD app, you need no algorithms knowledge at all -- rough and ready experience will serve. Even for data processing, unless you're processing truly vast (e.g. terabytes to petabytes) amounts of data, the algorithms you learn in an undergraduate introduction to algorithms class will work just fine. At this point, employers quite rationally want someone who can put together a combination of basic algorithms in 5 minutes over someone who takes a week to come up with an a elegant jewel of an algorithm that no one else at the company can understand. To put it another way, just like the slow food movement hasn't really made a dent in fast food culture, I don't expect a slow code movement to make much of a dent in the "ship yesterday" culture of modern software development.
- PaulHoule 13y agoPeople underestimate the difficulty of writing "boring" CRUD apps. I remember the bad old days, before Ruby on Rails, when we were writing Perl cgi-scripts to connect to the database, or when 100% of the time I'd inherit a PHP application the people either: (I) had magic_quotes_on which caused everything to be FUBARed or (II) didn't consistently quote HTML in forms or in SQL, so you could easily bust forms by typing in a " or '. Today the ideas in rails have spread to every other language, and it's better, but people still screw up database schemas every day. Steve McConnell's book "Rapid Development" is really about efficient development, which, in the grand scheme of things, takes about 10-20% more time than truly "rapid" development where you consciously spend more to compress the schedule over efficient development. Efficient development is a matter of getting things mostly right the first time rather than expensive "iterations" on a series of bad database schema designs when a system has customer data in it. Frankly, I've never seen a software project fail because the developers were too careful. I see them fail all the time when people set an unrealistic schedule and run around like chickens with their heads cut off and wind up taking much longer than they would have taken if they'd really practiced project management and design and all the other things that the usual (failing) company fails to practice.