I wish the article had a bit more meat to it. Not that this is a sin but he's just parroting things said in about 1000 other places by 1000 other people. Pen and paper good. Check. Daily journal. Check.
The OP is keeping a journal, so he has developed a real practice that works for him. I agree that a few sentences describing what he puts in there would have made this article stronger.
The second image of the journal page seems to show a list of possible approaches to a problem. The fourth image looks as if it has performance data and evaluation of a working system, so that is a couple of ideas. I think it is quite a brave thing to post the actual images. Perhaps fortunate the OP does not record team dynamics in his journal.
I work as a teacher, and I use a cheap page a day diary to record a few key points from each lesson. The 'readymade' aspect of the page a day diary seems to reduce the 'threshold' for making notes.
* Write a todo. Ex: Log errors from Fb.
* Ask a question if I'm stuck. Ex: Will Log4R block the reactor?
* Play with various approaches. Ex: Write in thread, plug into Goliath's logger.
* Note any bugs. Ex: Logger blah blah
* Rinse and repeat.
I know its a silly example, but you get the idea. Hope that helps.
I think the author has jumped to a foregone conclusion. He thinks it's all about getting releases before they're made public, and doesn't see any reasons other than that people might have for going with pirated entertainment.
The reasons are many and varied. Some folks simply don't want to pay, others are frustrated by the content providers insistence on their way or the highway.
This has always been Dave's problem. He's a Big Idea Guy, but his implementations often end up being somewhat less than fully thought through. I say this as someone who has been following him for way more years than I like to think about (I wrote a bunch of Frontier code WAAAY back in the Classic MacOS days :) As always though, he's thought provoking and gets other people discussing better ways to do it, which I think he entirely approves of.
Wow, the author of this article should be the poster child for wh Google's 2 factor should be de rigeur for anyone who actually cares about the contents of their email.
I disagree with the author on a number of levels. First and foremost, he/she's treating the editor as if its sole purpose in life is the invention of new code. This seems like a somewhat stilted view of reality to me. Features like syntax highlighting, syntax aware block indentation, and project aware search are easy wins in terms of ROI.
Also, they bemoan the fact that for many people their editor is also their primary code reading environment, but it sounds very much to me like what they're asking for is amply provided for in a modern IDE.
While I agree that fixating on a particular tool can be a waste beyond a certain point, IMO a programmer investing in learning their editor seems like time well spent to me.
100% agreed. alttab is falling into the common geek social trap of assuming that all the world is exactly like him/her. Personally? I couldn't care less about start-ups. I'm happy that they exist, I appreciate the innovations they create, and I enjoy the fruits of their labors, but to act as if the alpha and omega of existence is solving the problem of what causes start-ups to fail is IMO fundamentally both arrogant and wrong headed, because start-ups represent only a small percentage of the tech world at large.
Well, just learn ruby and read the source code of snappy, then write your own camera activation code -> no problem.
If you don't trust your link, go to the well known github website and search for the project yourself.
"With growing wish for self responsibility comes growing need for power."
I like the article as I am also a command line junkie, but I have an issue with it. I might be being pedantic here, but the fundamental premise of the article is a falsehood.
UNIX is in no way, shape or form an IDE. IDE stands for Integrated Development Environment and means exactly that. All your tools under one roof.
I do not deny and in fact would also assert that the separate tool chain / everything is a stream of bytes philosophy can be used in amalgam as an incredibly powerful methodology for software development, but that doesn't make it an IDE.
I typically tweak my rc files for a particular task ($language development, packaging, communications, system configuration, etc) and spawn a screen session with my $HOME pointing at a context-specific directory. This makes everything integrate a little better around the task at hand, while still giving me the full expressibility of my shell. I don't know whether I'd quite call it "Integrated", but I find it useful.
> UNIX is in no way, shape or form an IDE. IDE stands for Integrated Development Environment and means exactly that. All your tools under one roof.
agreed. if anything, it's a UDE: Unintegrated Development Environment. which is it's strength and weakness. the initial learning curve is steeper than with an IDE, maybe, but you don't run into these painful low ceilings like with an IDE. so much synergy & integratability in the CLI paradigm. pick and choose. customizable UX, custom workflows, automation, and typically much less opaque configuration, lower idle cpu and memory use, etc.
Two of them at least are fairly short: a run-through of Limbo takes about 3-4h tops, and you can go through Bastion in under 10 (although you'll need quite a bit more time to do everything and get all the achievements).
I've yet to finish the other 3 so I don't know how long they last.
The real issue here, as I see it, is that Apple needs to be 100% consistent about its app store approval process, and exceedingly clear when they yank an already approved app.
Why are they yanking it?
In a case like this, the reason seems pretty clear cut "Because you used an unauthorized AirPlay key" - but the way the current system works, Apple doesn't have to give a reason, they just pull the plug.
I am an unabashed Apple fan, but I think this aspect of the platform is broken and wrong and I wish they'd change their policies.
For a much less clear cut yanking incident, check out all the recent news on how they did this to iKamaSutra, which had no stolen copies of anything and got yanked for no reason at all, AND they refuse to work with the publisher to fix whatever violations may exist.
