Su-Shee
Joined 16 years ago
Karma
149
Submissions
31
Member since
Nov 26
Recent submissions
Comment · 12 years ago
Comment · 12 years ago
PC specs: anything which can run ssh and is at hand when I need it
OS: Any Unix/Linux will do
Source/Version Control: Whatever is used where I have to do some work
Editors: vi(m), no plugins
At the end of the day, I really only need some ssh, screen, a halfway decent shell, any versioning and a vi.
Also: Pen and paper to take notes and ANY simple GUI to run a browser is appreciated.
If I can have it, I'll take it all in UTF-8, please. :)
Comment · 13 years ago
Haha, I call them "Cassandra" usally. :)
I like working with them and having at least one on the team, because they're a great addition to the "naive optimist" or the "carefree hacker-fixer" who always see the solution around the corner - in a couple of minutes of course. ;)
And: There's a lot of tech scenarios where being overly careful and actually seeing the impending technical doom in every corner is an advantage.
Similar to the pedantry you get by the human robot, Cassandras have their place - and good management and coworkers know exactly where and how to take them.
Comment · 13 years ago
For those interested in the science/medical side of things:
* "Zen and the Brain" (written by a meditation practising neurologist)
* "The Buddha Brain" (about the neurological/physiological background of a couple of buddhist principles)
Comment · 13 years ago
Quietly, some geeks never stopped having their own services and didn't even get centralized in the first place... ;)
That's not really "the way forward", that's actually quite back to the roots. :)
Comment · 13 years ago
For small stuff CouchDB directly (with Jade as templating) or Smalltalk's Seaside, for larger stuff build for running the next decade Perl due to boring stability and backwards compatibility and least surprises.
Comment · 13 years ago
Perl 6 releases itself monthly for YEARS now.
Comment · 13 years ago
Many programming languages have a function for that to do that for you...
In Perl, it's called quotemeta (qw, qq and family, too), in Python and Ruby it's .escape... and there's always \Q ... \E to use...
I'm sure others have similar methods/functions.
Comment · 13 years ago
Absolutely.
The book doesn't just teach you regex, but the why, how AND the dialects. It gives you an overview over different tools and programming languages and their regex-related functions and methods.
On top, it contains a ton of examples, is very well written (considering the insanely dry and difficult to typeset subject :) and is very polished (I think it's in the 3rd edition by now..)
If you just google or experiment on regex, you usally get bad regex, badly crafted regex, brittle regex and make every single mistake the book prevents you from doing.
It's really one of the most worthwhile books of reading through - it's also an excellent handbook to look things up.
Remember that a lot of commandline tools take in regex too - grep, sed, awk, you name it - it's not just for use in programming languages.
Your favorite editor has regex too.
I simple don't know how people can live without; I'm using regex practically every day.
P.S.: And _after_ reading the book, you will understand why people yell at you when you parse HTML with regex but you will know how to do it anyways and at least not completely badly. ;)
P.P.S: And here's the canonical post to BUT OF COURSE you can parse HTML with regex from stackoverflow.. :) http://stackoverflow.com/questions/4231382/regular-expressio...
Comment · 13 years ago
THE single best ressource to really learn how to deal competently with regex is still Jeffrey Friedl's book "Mastering Regular Expressions".
You will profit from it for the rest of your career.
(There's also a Regex short reference and a Regex cookbook by O'Reilly...)
Comment · 13 years ago
You mentioned in passing that you have a feeling that Picasa isn't surviving for long due to it's "old-fashionedness".
Considering how important "usefulness" and "usability" are by now, maybe add a criteria along those lines - how large is the "your mom uses it and likes it" factor, how "contemporary" are the UIs, how much effort puts Google into polishing it (it does a lot with G+ and Gmail for example) - something like this.
Another criteria could be "level of integration" - how much can you use a Google product as a standalone project or how deeply connected is a product into another one (e.g. Picasa used outside of G+) - which might in the end indicate not a direct shutdown but a product's dissolution into another one.
Comment · 13 years ago
Looks like "killed by success". ;)
Couldn't get through with Firefox (haha) and my german VISA, too.
Also note that 55 Euros shipping is NOT the only option.. ;)
Comment · 13 years ago
You should add a section about how a beginner is supposed to install all the components you're using.
Right now, you're treating it like they're all "just there".
Comment · 13 years ago
My needs exactly.
Comment · 13 years ago
So far I'm just not using the Developer Tools at all, because they don't give me what Firebug does.
Debugger, Inspect and Web Console just aren't working well together, aren't interegrated smoothly into each other and I hardly can get from one to the other. I can't enable ALL of them at once.
If they _were_ like Chrome's tools or Firebug I'd wish for the features of Firebug's XPath and CSS extension: input expression, get matching elements highlighted.
So, either they have to be as useful as Firebug, or throw them out to keep FF lean for users who doesn't need them anyways.
Also "keep the DevTools as simple as possible" makes absolutely no sense to me as a Web Developer - I need those tools as GOOD as possible and as USABLE as possible with a specific range of features I've come to expect from Firebug and Chrome.
I mean, I basically live with an open Firebug during work...
Go on to reading the Toyota management style in itself, there's a couple of books about it, that's what many IT techiques are getting their ideas from.
It's mostly about finding your values so to speak and pinpoint what you really think makes up a good software development company - maybe your focus will be on organization, maybe on other things, so get an overview first.
These two articles are hopefully also an interesting nudge to think about many things:
http://www.computerworld.com/s/article/9137708/Opinion_The_u...
http://alistair.cockburn.us/Characterizing+people+as+non-lin...
O'Reilly has a very interesting book with analysis which practices actually work and why/how - sadly I also forget the title. There's for example a chapter about when and why pair programming works and when and why not.
Also, just watch carefully and learn to notice "good organization" - happens in surprising corners and niches and try to see WHY it's good.