And it explained to me, in clear terms, why Windows was such a buggy pile of shit. It was created of its culture.
614 karma · joined February 25, 2009
And it explained to me, in clear terms, why Windows was such a buggy pile of shit. It was created of its culture.
Why were the control systems running Windows? Because it has a GUI. This helps when monitoring control systems, and of course is the only platform Siemens' monitoring systems run on.
Personally I program Clojure, so there's not a lot of syntax to highlight--well, more than in scheme, for example--but I couldn't imagine life without brace matching (a dynamic kind of syntax highlighting).
I've always wanted a 'timed SMS' app where you can queue up text messages and set a time to send them. That way you can be enjoying happy hour while sending off 'stuck late at office' and 'leaving soon' messages without thinking about it.
Even better would be an app that plays background noise during your phone calls: airports, offices, taxis, stadiums. Dial up where you want to be for your call. Great for the 'still stuck at office' call, provided you could drown out the noise of the rowdy bar you're in. Last I checked, Android didn't have an API for that.
When this javascript code attempts to access the LocalStorage API, Chrome (rightfully) steps in and says: nope. This may be a new security feature, but is present in Chrome 30.0.1599.114 on Fedora.
The problem with SQL is that it is not an API, it's a DSL. Which usually means source-code-in-source-code, string concatenation/injection attacks, and crappy type translations ('I want to store a double, what column type should I use? FLOAT? NUMERIC(16,8)?'). Even as a DSL it's pretty low-brow: just look at how vastly different the syntax is between insert and update, or 'IS NULL'.
For all those who love SQL, consider having to address your filesystem with it. Directories are tables, foreign-keyed to their parent, files are rows. There's a good reason why this nightmare isn't real: APIs are preferred over DSLs for this use case. And so too for databases, because they are the same abstraction.
Don't get me wrong, I love relational algebra and the Codd model, but SQL just aint it. SQL has survived because of its one and only strength: cross-platform. And like all cross-platform technologies, such as Java bytecode and Javascript, its rightful place is a compilation target for saner, richer, more expressive technologies. This is why I always use an ORM and have vowed to never, ever, write a single line of SQL again.
I mean, investing in a startup that has a value proposition based on real scientific research is the same as investing in the research in the first place. Am I right?
Seriously, all the horror that is perpetuated in the name of Islam reminds me of the crusades. And all that nonsense should have rightfully ended in the middle ages.
However, I use it because I'm a vim user and clojure has never had stellar support in vim (whereas Light Table--or rather CodeMirror's editor--has vim bindings). If you're an emacs user, Light Table might not offer anything over existing emacs tools.
if (strcmp(buffer + position + 5, "$ref") == 0) { / DBRef */
Seriously?My advice to anyone who doesn't like their job: please don't come to work in a shitty mood all the time, bitch and moan, and spread your poison around. You don't have to love your job, but quit making excuses and being lazy and go get yourself one you will love.
Edit: oops, this idea was already mentioned by akkatirk elsewhere in this thread.
"Philosophy teaches abstract thinking--how to manipulate and reason about purely abstract concepts; how to logically construct and analyse models of world (and being-in-the-world)."
I probably kissed a little arse too.
1. Give a confidence value: 'this can be completed in x hours with 50% confidence, or y hours with 85% confidence (where y > x)'. If you don't want to work in 'confidence percentages', translate that to a range: 'this can be completed in x/2 - x*1.5 hours'.
2. Never, ever quote on something you've never done before. Does the project require using a new API? Write a small, isolated test application that uses the API in similar ways. This will sharpen your confidence value. If you don't have time to exercise all the parts of the project you've never done before, shrink your confidence value but explain why: 'this can be completed in x hours with 20% confidence, but with a little more preparation time, I can get you a more accurate quote'.
Most importantly: be professional with your quotes. Don't take on too much just to be the hero who moved mountains and saved the day. No-one will thank you if you do (after all, you're just doing your job), and your professional image will take a dent when you don't. Also, as soon as you realise you can't make your confidence value, don't keep it to yourself. Yes, you'll piss people off by lagging the project, but the alternative is much worse. Not speaking up when issues arise is an ego problem (similar to being the hero who moved mountains).
Yes quoting is hard, but is required. Don't worry, developers are not the only ones who struggle with it. I work for a (non-software-) engineering firm that is currently taking a $1.6M+ bath (and rising by the hour) because they botched the quote process. Shit happens all the time.
How you do it is most certainly what matters to developers, as soon as it doesn't work as expected :)
http://programmingpraxis.com/2009/08/13/the-daily-wtf-malici...
It also says a lot about what is not valued: a consistent UI paradigm (Bootstrap not withstanding), a rich suite of client-supplied services, multi-tasking, static typing.
Javascript is just what you have to put up with to get access to everything else.
(or someone
(except 'Apple some-company))
As a general style, although somewhat inverted, I prefer 'tailing syntax': (or
(except someone 'pg 'rtm '_sh)
(except some-company 'Apple 'Weyland-Yutani))Also, the correct link is http://phantomjs.org/
Well, your free state is in jeopardy. Now is the time to assemble your well-regulated militia to secure it!
My point was the mental model I refer to when using $lambda is simpler and easier to understand than my mental model for syntax-case, syntax-rules, syntax-parse and friends. The very fact that 'Racket's macros can be entirely compiled away' complicates my mental model which must now accommodate 'phases', compile-time/run-time dichotomies, require for-syntax, etc.