752 karma · joined March 4, 2009
[ my public key: https://keybase.io/skyronic; my proof: https://keybase.io/skyronic/sigs/6ld4MkNiejCqvm00oXosdjR1zyplfCzQvLZolV0RYH4 ]
https://chrome.google.com/extensions/detail/laankejkbhbdhmip...
I haven't been programming a lot but here are some ideas that I've found, in similar vein to the parent article.
1. Watch Bram Moolenaar's talk or read his notes - http://www.moolenaar.net/habits.html . Essentially learn how to use your text editor, as that's the thing you're going to be spending a good deal of your time in. In three steps, his suggestion is - Find what you're doing repeatedly, automate it and bind it to a key, make it a habit.
2. use a good version control system. Use a DVCS like git/mercurial/bzr and make lightweight branches for even the tiniest little features. That'll allow you to multitask like crazy! If you start properly using branching, you can write more code quickly and safely and switch between contexts.
3. Make sure your build system is optimal. If you spend too long waiting for builds to take place, maybe you can explore options to make it better.
4. The most important productivity secret imo - ACTUALLY WRITE CODE. Don't think about writing code, don't read blogs about writing code, don't follow twitterers who write code. Most importantly, don't get distracted and idle away when you're trying to write code.
I have some amount of mastery over my text editor, my language, my OS, etc. But none of that compares to the mastery and discipline of sitting down, concentrating and not letting your mind wander too much - something that I am trying to attain, but it's harder than I would like it to be.
Let's say I have around 2000-3000 regular users. If there is some family emergency which is unplanned and requires me to be there, I won't be able to maintain anything for about three-four days, except maybe make sure that the servers don't go down.
I would ideally like to let the users know that there's a problem right now. Despite everything, most of them will understand. However how far do I have to go to tell them? Do I send out a little tweet, an email, or put a persistent message on the website?
I know that it varies vastly according to context, but what would be a rough estimate on the best way to handle a situation like this?
By saying things like "And who cares about law school or baseball teams", you are belittling a whole set of people. Saying "sailing solo is more admirable than working towards law school" might be accurate, but the way I read it - "law school? You haven't sailed solo around the world, hence your existence is invalidated".
As for the troll remark, you're a new user with no real identity making relatively controversial and somewhat personal statements with a relatively disrespectful tone. I'm not too sure what the textbook definition of a troll is, but this is the closest one I've seen over here.
I find this trend rather disturbing. It's almost parallel to the "nerds don't get laid" paradigm. For the record, I'm a physics major. And I'd any-day prefer to be a little-league team manager than troll on comment threads.
Remember when http://delicious.com was http://del.icio.us When I first saw the product, I thought the name was "icio".
I can think of several disadvantages (though I may be wrong and naive):
1. If you're running a node, and I'm running a node, my data schematics might not be compatible with yours. If I write a uniform backward-compatible RPC, then it'll be a little better.
2. I can't selectively allow you to copy some data (photos) and not others. If you are a user on my database, you can access everything you have permissions to. It's hard to set fine-grained permissions.
3. Push notifications will be hard. I'd have to poll the database for changes.
For that matter, the same can be achieved by putting a giant XML file on Git, and having each person set up a remote, or using a complicated set of shell scripts and rsync. Couch's replication facility is really neat, especially if you want to scale horizontally or if you're adding redundancy, etc.
CouchDB is becoming the new hammer. It'll get tempting to write source control, file backup, etc, using this database because of the data sync, and decent query capabilities. But I feel that building a social network on top of CouchDB's replication might not be the best of ideas.
That's why I told everyone about my idea - presented it in startup events, showed people demos, put it up on public mailing lists and wikis. The idea got battered and beaten down and each time there were little changes. There's this huge hype about being a "stealth startup" and a fear that people in some web shop will steal your idea and clone it.
tl;dr - the idea that you start with is the one that people can't completely tear apart and obliterate.
Also, the idea is pretty much useless. If I had an idea that I'll make a touch screen phone with an app store, nobody would've taken me seriously. If I'd pulled an apple and built one, people would've. Three months into full-time development of a product, I can only say that execution is pretty much everything.
Things like strongly binding data to objects, thereby reducing load significantly is embarrassing and tragic. Real developers should do it the old fashioned way - make a model class, write forms, data mappers, sanitizers and validators by hand - who cares if you have to change it in four places whenever you need to add a new field, atleast you're not doing it the M$ way.
Thank you for taking the time to point this out.
That kid would have the time of his life saying "Open solitaire" loudly and clearly into the microphone a gazillion times, and the system would interpret it as "delete my homework" or "email grandma all my private files".
All this seems pretty neat, but when it comes to just getting a little work done - I'm still skeptical about how much advantage touch, motion, gestures, speech, etc will help.
I am very excited about gaze tracking though. I don't think it's too long before I can switch from one window to another by just looking at it and twitching my eye.
I too feel that they need to experiment and push the envelope forward. But Canonical doesn't seem to have _that_ many developers that they can focus on too many items. Of course it's run by some very experienced people, and I'm not one to complain. This seems more like a cool hack which can spawn off an independent community project which might eventually become part of the desktop.
Think about it - a gesture can mute the sound, so you don't need to pause the music when a phone call comes in. Get up and leave, and the screen will lock itself. Stick out your tongue and it'll check your email. Heck, I'm sure soon enough Ubuntu will detect your face seeming sad during debugging sessions and automatically shows kitten pictures (Emacs probably does this already, I'm not sure).
In fact, I would appreciate if there was a way to make static files (like js and css) location-agnostic.
I could say: <% Html.Stylesheet ("styles/foo.css") %> and it'll map to /Content/styles/foo.css or my nginx server or my Amazon cloudfront storage, etc.
After building a moderate sized application (currently around 5-6k LOC) in .NET MVC2, some of Jacksonh's decisions start to make a little sense. However, there are a lot of situations when a paradigm seems neat but in reality it might not be _that_ useful.
For instance you can respond to queries using Lambdas/Anonymous delegates like Get("/foo", ctx => ctx.response.write ("foo")); YAY! I made a HTTP Response in just one line.
But looking at about 17 different endpoints I have in my application, not one will benefit from this feature. In the current model, I may spend a minute or two defining an action and specifying the route, but will spend atleast half an hour implementing it. For some reason, everyone seems to be focussed on cutting down the two minutes to one minute.
Also, this means that the routes aren't in one place. MVC2 has named routes and I can quickly change things from a single function. I used to like Flask's technique of making routing easier by simply specifying the route as a function attribute/decorator - but this made maintaining it quite hard.
Also, this tries to do everything. For instance, it allows you to serve static files as well like -Route ("/Content/", new StaticContentModule ()); When I have something like nginx which is known to serve files in a very efficient manner, there isn't any reason why I'd choose to let this server do it.
This seems fantastic for a quick hack and a tiny mashup, but for anything bigger, I'd definitely give it a second look.
These are tools built around the language and the workflow, and thus have been extremely tailored to ensure that productivity is high. While you can type the code out in any editor, and maybe even get CTAGS based completion and jump-to-type support, I haven't seen as tight an experience as MonoDevelop or Netbeans (or VS, but I don't know that very well).
There exists a tradeoff - you won't get the extensibility of Emacs or the efficiency of vi (they have vi-modes but it doesn't come close). Ultimately, when it comes to simply getting the idea from your head into the code, IDEs do help a lot.
Initial benchmarks showed that the performance isn't that great compared to the same application running on Windows, but compared to similar applications on rails and django show that performance is comparable, even better than the dynamic frameworks (which is somewhat obvious since it's compiled).
Haven't profiled for memory leaks though.
Can you please elaborate with some details about how "broken" python is on systems, and the situation with python 2.4? According to the article, "recent Ubuntu releases" had broken/deprecated python installations. A quick search reveals that python 2.5 has been shipping as the default "python" meta-package(?)
http://packages.ubuntu.com/search?keywords=python
Can you also please elaborate any "features" that the install was missing - are these specific modules ?(I think python's sqlite3 is missing by default on Ubuntu. I'm not too sure.) I'm not questioning you or anything, I'm just slightly concerned as we had plans to ship a Python application, and when someone experienced enough has a valid complaint, it makes sense to understand the basis behind that.
Well, Taking all my close friends, who might be comfortable working with me - and filtering out those who are from a CS/Programming background, exhibit genuine hacker mentality, can delay gratification sufficiently by not immediately jumping into a well-paying job, and can work in a similar pace as mine - I'm left with a pretty small set. And that set didn't graduate with me, so the argument that the very fact that I don't have anyone starting a company with me does not sufficiently imply that my idea is poor or that my convincing skills are sub-par might not be perfectly valid.
I agree with most of the things that PG writes about, (who doesn't?), but I find something wrong on a fundamental level with the justification of why single founders are a bad idea.
From a single founder, I fear there are other reasons why a startup might potentially fail with a single founder:
* One might get too easily tempted to quit, and won't get easily talked out of it. * There's nobody to push you to work when you're feeling lazy. This can lead to a lot of time being wasted. * Ideas need to be bounced back and forth. They must be criticized again and again until no criticism can be made about them. There's nobody to do it with here. * If you have co-founders you always have company if you want to get some coffee, or play something outdoors :)
I'm hoping that once I launch and am able to demonstrate my abilities and ideas (or the lack of them), I might be able to find people who are willing to work. I look forward to saying "Hey, do you want to help me improve this great product which is doing quite well" instead of "Hey, do you want to drop everything in your life and hack on my neat idea".
I hit up all the networking events - barcamps, startup events, and other miscellaneous meetups. I met a lot of people, offered to buy them beer in exchange for hearing out my idea, and made some great friends. The people who were capable and experienced were already in a job, or a startup of their own. The ones who were interested to join me were ready to do it part-time and half heartedly. The two people who were enamored by the idea and wanted in couldn't code for nuts.
Two months later, I am still single, two weeks away from launch, and things are going great. I have some unconventional little discoveries by my tiny amount of experience:
1. Go somewhere you'll be surrounded by people. I went back to college and have friends all around. In the event that I get bored or need to take a break, a coffee break with five people is just a phone call away.
2. I realized that it's hard to stay fully motivated through the entire thing. Talk to your friends and family about it and tell them it'll take their help. My parents were extremely helpful, and my mother patiently used to listen to my ideas, even though she couldn't really understand what an alpha release is.
I actually found some minor advantages of being a single founder. For instance - you get the flexibility to travel around and relocate if you want. But the disadvantages far outweigh the advantages.
In programmerspeak - I felt being a single founder instead of having a co-founder is somewhat like writing a web application in C++ instead of Rails. It's harder, though not impossible. And you learn a lot more about yourself and your limits.
http://www.wolframalpha.com/input/?i=0+degrees+kelvin+%2B+0+...
Funnily enough the original query is handled well[1] by W|A:
http://www.wolframalpha.com/input/?i=0+degrees+celsius+%2B+0...
And the query that fails in Wolfram Alpha, works fine in Google's Calculator:
http://www.google.com/search?sourceid=chrome&ie=UTF-8... :)
1: By "well", we probably mean according to intuition
However, since this solution isn't spectacularly scalable, I'm not too worried.
Heck, this is perfectly possible with LinkedIn and twitter as well. I don't understand what the fuss is.
I've got $EDITOR set to "gvim --remote --wait" which means that the file is opened in an existing instance of vim. Unlike "gvim --remote" which will return control to the shell the moment the file is opened in gvim, the --wait option forces the command to wait till the file is closed (which is the standard expected behavior for most things like writing git commits, etc).
Now the interesting problem is that I have to kill the buffer rather than quit the editor. so I do a :w and :bd to delete the buffer, which makes sure things go fine on the shell.
Sometimes, if I have opened the file in a split (which is invariably the case), using :BD will ensure that my split isn't closed as well, when the buffer is killed.
Plus, BufExplorer has a very neat little trick which I just discovered recently. Sometimes I can close a buffer and might have to reopen it. So I bring up Bufexplorer and press "u" to undo changes, and I can go reopen any of those buffers.