Skip to main content

Stars out, dzone in

A few weeks ago, I turned on blogger.com's rating gadget. A nice toy, but really only that.

Since I started writing for agilesoftwaredevelopment.com, I have learned to appreciate the value of social networking sites in general, and dzone in particular.

DZone is a digg-like site, where you can submit and vote on the links relevant to developers. You can vote articles up and down (which I appreciate for the feedback) and the good articles are shared with other developers.

So when you read an article:
  • if you hate it give it a thumbs down (to keep people away and tell me never to write such trash again) or 
  • if like it, give it a thumbs up, and share it with the developer community!

Comments

Artem Marchenko said…
Good move! For SW development related articles I like DZone much more, than Digg.

Eh, if only DZone would really store my login information not to login very often.
Sean said…
Ha! I have that same problem, and it results in me not logging in at all most of the time.

Even when I tell firefox to remember my password so I can just hit login it doesn't work... I think it is because of the lightbox...
Evgeniy said…
After they have implemented Lightbox login, I had to write simple GreaseMonkey script to take plain login page back. I now try to post its code here; not sure if Blogger engine won't break it.

// ==UserScript==
// @name DZone plain login page.
// @namespace http://www.unchqua.ru/ns/greasemonkey
// @description Take back plain login page.
// @include http://www.dzone.com/*
// ==/UserScript==

// UL which holds "log in" link.
var ul = document.getElementById("mh_login");
if (!ul)
return;

// All A elements in it.
var anchors = ul.getElementsByTagName("A");
if (!anchors || anchors.length == 0)
return;

// URL prefix to participate in link search.
var URL_PREFIX = document.location.protocol + "//"
+ document.location.hostname
+ (document.location.port > 0 ? ":" + document.location.port : "");

// Look for needed A and replace its href attribute.
var anchor;
for (var i = 0; i < anchors.length; i++) {
if (anchors[i].href == URL_PREFIX + "/links/loginLightbox.html") {
anchors[i].href = URL_PREFIX + "/links/login.html";
anchors[i].className = undefined;
anchors[i].onclick = undefined;
break;
}
}

Hope this will help.

Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …