j-kidd

Feel free to get one of this http://zh.wikipedia.org/wiki/黄帝内经 and knock yourself out.

According to ancient Chinese wisdom, a day is divided into twelve 2-hours slices, and one is supposed to be:

- falling asleep during the slice from 9pm to 11pm

- remaining sound asleep during the slices from 11pm to 1pm and from 1am to 3am

- waking up during the slice from 3am to 5am

> We can't easily know the state of the code, but we can easily read the number that you have assigned it.

Exactly. To those who have been using 0.6.0_rc*, version 0.6.1 conveys the meaning "go ahead and upgrade, here's the stable release with no backward compatibility issue".

You will get your version 1.0 after several pre-1.0 RC releases. That's the proper release management.

It is easy to feel overachieved when the deadline is tight. What we fear is to under-perform when given ample resources, when "it's on".

Yea, this madness about github profiles must stop. I cringe every time I see someone here pimping some github "projects" they whip up in minutes which obviously they have no passion in.

Well, the title is "Nginx Vs Apache in AWS", not "Nginx from apt-get Vs Apache from apt-get in AWS". If you can't install the latest stable releases, then don't write a comparison about them.

Actually, the title:

"Why Amazon Hired the Lead Architect for DB2 and SQL Server to Run Its Cloud Empire"

would instill much less confidence than the current one, consider how bad those products are compared to one that has proper architecture (i.e. PostgreSQL).

Sad to know. `httpd -k restart` was available since the beginning of time.

This has a simple explanation. Heroku was targeting the ruby-on-rail crowd, which more or less belongs to the "Stupid Rich" quadrant when it comes to hosting / deployment.

Meanwhile, AWS has been a dominant presence in the "Stupid Poor" market segment.

The other two quadrants do not exist.

SQL Server is anything but well engineered. What version of SQL Server are you currently running? Is it on the latest service pack only, or with the latest cumulative update applied? The later fixes critical bugs, but claimed to be "not fully tested" by Microsoft. This retarded release policy means there is no stable version of SQL Server.

Great article. The most interesting part for me is that the JSTOR servers couldn't sustain continuous download from a wireless connection. If only they have more competent developers...

Just read the Chocolatey vs Ninite comparison [1]. For me, the biggest selling point of Chocolatey is its decentralized nature, making it useful for enterprisey deployment.

[1] https://github.com/chocolatey/chocolatey/wiki/ChocolateyVsNi...

Because space is not just another character. Space separates args.

From their FAQ, it says that chocolatey is "CLI focused". So, "C:\chocolatey" makes sense. Paths with space are definitely less CLI-friendly than those without.

Actually, it is pretty common to replicate the transactional data into another data store for analytical purpose. However, using PostgreSQL as the OLAP data store may not be the wisest move.

> People are scaling OUT not UP. Especially startups.

Startups need to scale out because many of them like to deploy on mediocre EC2 instances with the slowest SAN storage ever.

People that keep recommending PostgreSQL are rightfully ignoring this industry.

While the original article is unfair, I do think that the ratio of good programmers to bad ones is higher in the valley, thus the smugness.

This is more like "valley versus the rest of the world", instead of "US and A versus the rest of the world".

You are comparing library with language here. Rails is vulnerable to remote code execution. This is comparable to something like:

https://bugzilla.redhat.com/show_bug.cgi?id=854757 - CVE-2012-4406 Openstack-Swift: insecure use of python pickle()

I have never done any Ruby / Rails development, but this exploit doesn't look like it requires any proof-of-concept.

My understanding is that as long as there is a JSON endpoint accepting parameters, and the parameters are used for query generation without going through a proper validation layer [1], then the app is vulnerable.

[1] In python, this would be things like FormEncode, WTForms, Colander, etc.

> Someone who considers the handling of formatting and style to be the "biggest" is likely to be one who values those things highly.

Not really. Someone who values those things highly would have written the code as such, instead of relying on a utility to reformat the code.

> I'm pretty sure Hibernate uses parametric, prepared statements. I believe SQLAlchemy and Django ORM do not, but use their own escaping mechanism internally.

You have no credibility to talk about database if you can't tell what kind of statements are being executed.

Just because you got yourself into the mess, doesn't mean that database schema is suddenly bad. Data definition language (DDL) is a declarative and well thought-out DSL that can guarantee the business logic to a certain extent, at a very very low cost.

On the other hand, stored proc is a relic of the integration database [1], and is definitely less flexible compared to using your programming language of choice.

Instead of jumping from 2000 tables / 45000 stored procs straight to "schema in code", perhaps a saner tables design with no stored proc is the better way to go?

[1] http://www.martinfowler.com/bliki/IntegrationDatabase.html

I can change them trivially in KDE, so there is no need to stick the commands in .xinitrc. FYI, allowing mouse acceleration threshold to be set to 0 was added in year 2003 in KDE:

https://bugs.kde.org/show_bug.cgi?id=31189

Anyway, I certainly agree with your opinion. It is just that I think E17 is more than a window manager, and I would place it in the same category as XFCE.

Just tried E17 for the first time. Kinda bummed that the control panel doesn't allow setting mouse acceleration threshold to 0. Also couldn't find a way to change keyboard repeat delay / rate.

Looks like more thought was put into eye candy than input dev.

While your point is valid, I didn't expect this to happen with requests. Just two weeks ago, I was telling my colleague that requests is such a nice library, we have nothing to worry about when installing a new version. Simply grab the latest!

Then 1.0 happens. I have now moved requests to the "thoroughly test before upgrade" pile.

This is why we should maintain our own pypi repository. Your external dependency did nothing wrong.

Look out for the change to the Request constructor that makes `url` no longer the first parameter. Rather poor backward compatibility there.

If someone never outgrows it, it drags the whole team down by constantly having to answer the most basic of questions.

You are describing EC2. Most other providers do provide proper persistence.

> And it's the office where people sit by each other's desks all the time is where work gets done.

Then I wonder how projects like Linux kernel, KDE, Python, etc manage to get any work done.

In software development, I think the most important communication needed is to do everything in the open. This means things like a ticketing system so that everyone knows what everyone else is working on, a continuous integration system that permits deployment only if all tests pass, a wiki system to share various insights, etc.

Currently, I work in an open plan. Information hoarding is the norm here, despite chatters going on all days long. Open communication is a concept that has nothing to do with open plan.