Researchin’ the day away…
Entries tagged with “programming”.
Posted by Ross at 6:39 PM under 1
No Comments
Writing is harder than hacking. They’re both hard to do well, but writing has an additonal element of panic that isn’t there in hacking.
With hacking, you never have to worry how something is going to come out.
Working on my thesis proposal this week; my thoughts exactly.
I’ve created a JavaScript class (Base.js) that I hope eases the pain of JavaScript OO. It’s a simple class and extends the Object object by adding two instance methods and one class method. The Base class defines two instance methods: extend Call this method to extend an object with another interface: var object = new Base; object.extend({ value: "some data", method: function() { alert("Hello World!"); } }); object.method(); // ==> Hello World!
Photoshop, Premiere, Maya, AutoCAD, ProTools, Finale, Reason, PageMaker. These are the state-of-the art tools for creators. They are all rich, powerful, versatile programs that strive to work at the artist’s level of thought. And the people who write this amazing software get to use… Visual Studio? Eclipse? Emacs?
The Logical AND operator (&&), will return the value of the second operand if the first is truly: true && "foo"; // "foo" And it will return the value of the first operand if it is by itself falsy: NaN && "anything"; // NaN 0 && "anything"; // 0
So my basic rule for software release cycles is: Set a ship date, which might as well be arbitrary Make a list of features and sort them out by priority Cut low-priority features every time you slip so as to make the date.
It's hard for anyone much younger than me to understand the fear Microsoft still inspired in 1995. Imagine a company with several times the power Google has now, but way meaner. It was perfectly reasonable to be afraid of them. Yahoo watched them crush the first hot Internet company, Netscape. It was reasonable to worry that if they tried to be the next Netscape, they'd suffer the same fate. How were they to know that Netscape would turn out to be Microsoft's last victim?
Even though we’ve changed the date variable referenced by the block, when the block is called it still prints the original date and time. It’s as if time stood still when the block was declared. And that’s effectively what happens. As execution passes over the point where the block is declared, the block takes a (read-only) snapshot of all the variables in scope that the block uses. You can think of the value of the date variable as being frozen inside the block. Therefore, whenever the block is called—immediately, 5 seconds later, or just before the app quits—it always prints the original date and time.
Recently shared“Why do we love efficiency and speed so much? If the end of the game is death, the most efficient thing to do is die. The point is to live.”
— Joi Ito
Follow me on twitter