Donald Ferguson commenting on why Websphere was his "biggest technology mistake:"

Because I had come from working on big mission-critical systems, I thought it needs to be scalable, reliable, have a single point of control ... I tried to build something like a mainframe, a system that was capable of doing anything, that would be able to do what might be needed in five years.

I call it the endgame fallacy. It was too complex for people to master. I overdesigned it.

Because we were IBM, we survived it, but if we'd been a start-up, we'd have gone to the wall.

Pyramid is a small, fast, down-to-earth Python web application development framework. It is developed as part of the Pylons Project. It is licensed under a BSD-like license.

pyquery allows you to make jquery queries on xml documents. The API is as much as possible the similar to jquery. pyquery uses lxml for fast xml and html manipulation.

A manager went to the master programmer and showed him the requirements document for a new application. The manager asked the master:

"How long will it take to design this system if I assign five programmers to it?"

"It will take one year," said the master promptly.

"But we need this system immediately or even sooner! How long will it take if I assign ten programmers to it?"

The master programmer frowned. "In that case, it will take two years."

"And what if I assign a hundred programmers to it?"

The master programmer shrugged. "Then the design will never be completed," he said.

The short answer is that OpenID is the worst possible "solution" I have ever seen in my entire life to a problem that most people don't really have.

That's what's "wrong" with it.

...

OpenID is not flawed in some minor product way that requires just a few tweaks, it is so massively flawed (perhaps in its very conception) that anyone in their right mind would immediately know that it could never possibly be successful, the very notion that there's merely "something wrong" with it is a Joseph Goebbels -"Big Lie"-style question wherein the nerds who came up with it have somehow been brainwashed into thinking that it could somehow ever be a viable thing that real people would want to adopt.

JetBrains PyCharm — Python IDE with complete set of tools for productive development with Python programming language.In addition, the IDE provides high-class capabilities for professional Web development with Django framework.

This is a follow up post to How Hacker News ranking algorithm works. This time around I will examine how Reddit's default story and comment rankings work. Reddit's algorithms are fairly simple to understand and to implement and in this post I'll dig deeper into them.

The first part of this post will focus on story ranking, i.e. how are Reddit stories ranked? The second part of this post will focus on comment ranking, which does not use the same ranking as stories (unlike Hacker News), Reddit's comment ranking algorithm is quite interesting and the idea guy behind it is Randall Munroe (the author of xkcd).

Someone who knows how to search for code examples and how to learn from the work of others will be more or less self-sufficient. They can learn and grow their skills on their own without needing someone else to do it for them. The ability to learn and grow your knowledge is the single most important skill for any developer. Without the ability to grow you will find yourself quickly deprecated. I do expect people to know how to use the language and/or framework they were hired to work in, but I judge them primarily based on the work they submit. A guy who can figure out how to do things that he doesn’t know how to do, on his own, on the fly, is a real programmer.

This is a set of apps which creates the same application in various Python web micro-frameworks.

...

Microframeworks:

* appengine * flask * web.py * juno * bottle * itty * tornado * pyroutes

Full stack frameworks:

* django * web2py * pyramid

Using Evidence-Based Scheduling is pretty easy: it will take you a day or two at the beginning of every iteration to produce detailed estimates, and it’ll take a few seconds every day to record when you start working on a new task on a timesheet. The benefits, though, are huge: realistic schedules.

Realistic schedules are the key to creating good software. It forces you to do the best features first and allows you to make the right decisions about what to build. Which makes your product better, your boss happier, delights your customers, and—best of all—lets you go home at five o’clock.