“If you’re building a technology-driven company, you better have a culture that loves engineers, and I mean love. All too often, I see entrepreneurs who say they “just need engineers” to “bang out the code” for this great idea of theirs. If you view engineers as interchangeable factory workers instead of partners and creative people, you’re in for a tough time getting huge in a world driven by technology.”—Scaling startups (via adactio) (via solipsism)
“Don’t cry. Code, monkey. Code code code, code until you fucking hate it. Release it. Drink yourself into a weekend of oblivion. And then code some more, code out the bugs, code in extra features: answer emails, bug reports, requests, feedback, code code code code code.”—smaps comments on reddit (via solipsism)
“Set a duration of how long you think it should take to solve a problem”—
C’mon, admit it! I’m just as guilty as the next programmer. I’ve seen programmers sit in front of a monitor for eight hours at a time trying to solve a particular problem. Set a time table for yourself of 1 hour, 30 minutes, or even 15 minutes. If you can’t figure out a solution to your problem within your time frame, ask for help or research your problem on the Internet instead of trying to be super-coder.
“In computing, the second-system effect or sometimes the second-system syndrome refers to the tendency, when following on from a relatively small, elegant, and successful system, to design the successor as an elephantine, feature-laden monstrosity.”—Second-system effect - Wikipedia, the free encyclopedia
I’m a big proponent of programming being accessible to everybody. I’ve linked to this article in the past and quote Marc Prensky in my talks sometimes. To me this is obvious, but I don’t think it’s a view shared by too many.
As programming becomes more important, it will leave the back room and become a key skill and attribute of our top intellectual and social classes, just as reading and writing did in the past. Remember, only a few centuries ago, reading and writing were confined to a small specialist class whose members we called scribes.
“As programming becomes more important, it will leave the back room and become a key skill and attribute of our top intellectual and social classes, just as reading and writing did in the past.”—Marc Prensky
“Parsers are invoked upon an input stream. They will consume a certain number of tokens and then return a result along with the truncated stream. Alternatively, they will fail, producing an error message.”—
Conceptually, a Parser represents a very simple idea.
“Most programmers code up FETCH operations all over the place and do not ever realize they are denormalizing. I think this pattern is just so natural that most of us never think about it. If you examine your database applications you will likely see that you are doing this all over the place.”—The Database Programmer: Denormalization Patterns
There’s been lots of discussion recently about finding other HNers to talk to / bounce ideas off / work with, some Google spreadsheets were set up to share details but they were soon vandalised. I had a spare afternoon yesterday (which turned into a long day) and here’s the result: