1,906 karma · joined June 21, 2007
1- http://en.wikipedia.org/wiki/The_Cartoon_History_of_the_Univ...
What sort of byte? Mine only represent integers from 0 to 255.
More seriously, I don't buy your implied argument that plain text representations are less compact. Whether or not this is true depends more on the specifics of your domain and the system you use. For much of the data I work with the strongly typed database representation is often larger then the plain untyped (ASCII) source.
Even if your data is not a good fit for the relational model, it's often a good idea to rely on a database system offering features such as transactions, an ad-hoc query facility, enforcement of access permissions and update policies, replication/recovery, efficient I/O, etc.
Even if it keeps you up all night,
wash down the walls and scrub the floor
of your study before composing a syllable.
Clean the place as if the Pope were on his way.
Spotlessness is the niece of inspiration.
The more you clean, the more brilliant
your writing will be, so do not hesitate to take
to the open fields to scour the undersides
of rocks or swab in the dark forest
upper branches, nests full of eggs.
When you find your way back home
and stow the sponges and brushes under the sink,
you will behold in the light of dawn
the immaculate altar of your desk,
a clean surface in the middle of a clean world.
From a small vase, sparkling blue, lift
a yellow pencil, the sharpest of the bouquet,
and cover pages with tiny sentences
like long rows of devoted ants
that followed you in from the woods
Billy Collins, Advice to WritersWhen this starts to happen what I do is start making my own private scrumm burndown chart at the beginning and end of each day by adding a few rows to a spreadsheet with the estimated hours remaining on each of my development tasks along with a note on how I actually spent my day. I then review this with my boss and ask him whether or not he thinks I've been prioritizing properly and leave it up to him to adjust everyone's expectations (which is usually easy because I make sure to keep good records and structure our communications).
But while I'm fortunate to be working in a good team, there's no denying the psychic toll of constant task switching is disruptive. Unfortunately I know of no easy solution other than to spend the time to re-focus. Sometimes it can take a whole day of just re-reading code, making notes and fiddling around writing and rewriting little things before I can get back into a solid productive development flow.
The Power and the Glory by Graham Greene
I choose the latter which turned out to be a big mistake. Not only did I walk away from a small fortune but nothing went right at the new company. Even though I did my best to secure everyone good offers, as a whole the team was unable to work together. Everything fell apart when a key partner we were counting on to raise funding instead used our ideas to help secure a management position at a competitor.
In the next company I start, I will be much more careful in who I hire and who I choose as a partner.
What I'd really like to know, ideally from someone who has worked with both, is if there are any particular features one or the other offers that actually do matter.
Or perhaps this is an example of where developing good PR is more important than focusing on features?
Perhaps I should rephrase my question: what makes Stack Exchange worth the price they charge when Slinkset is free?
Do APL derivatives (J, K, APL2, A+, ..) count as APL?
1- http://www.xcf.berkeley.edu/~wei/viola/aboutEolasMicrosoft.h...
Actually I think in most cases the simplest and most efficient architecture is when your server creates a process for each specific type of thing it needs to do and then simply delegates incoming requests. http://www.okws.org/doku.php?id=okws is a good example.
However if the question you're really asking is "can those technologies help me reduce my effort or cost by 80% ?" then thanks to advances in hardware, services and open source in many cases the answer is yes.
1- http://research.microsoft.com/en-us/um/people/gray/talks/gra...
Everywhere I've ever worked I've encountered some variation of this. One recent customer had some MySQL problems which took down the sole MediaWiki server holding all their IT documentation. Not only did they not have a standby, not a single backup or dump was ever done.
These days what I find even more astonishing is how even experienced professionals make the mistake of thinking they don't need separate backups because their system has some integral disk redundancy (e.g. http://www.joyent.com/joyeurblog/2008/01/22/bingodisk-and-st... ).
Here is a light interview (by none other than Jim Gray) on this published in ACM Queue from 2006.