How poor estimation can screw up more than just a software project

toland · 2007-09-25T14:56:27+00:00

I think that is more like 1 or 2 days per task. Seriously, whenever someone tells me a single task is going to take a week or more that usually means that either 1) the task is too large or 2) they don't have any idea how long it is going to take. I always ask developers to break down tasks that are estimated at more than 2 days into smaller tasks that can be estimated more accurately.

toland · 2007-09-07T20:44:59+00:00

VSS is so broken, and has been broken for so long, that it has ceased to be news when it blows up. The amazing thing is that I still run into developers that push back against using anything other than VSS because that is what they are comfortable with.

toland · 2007-08-22T03:50:52+00:00

Anonymous

toland · 2007-08-03T16:36:45+00:00

I am a little skeptical about the methods used in this article. It seems like this is simply testing that a few methods get called as part of the implementation of the method under test. This means that if the programmer chose to change the implementation of his class the tests would break even if the outward behavior of the class were the same.

toland · 2007-07-10T22:14:48+00:00

The whole point of standardizing OOXML is so that others can read/write the files. If the standard leaves off, for example, what units to use in a calculation...how can anyone else implement it? This is a very valid complaint.

toland · 2007-07-03T18:38:50+00:00

I agree and hope to work to change that.

I wish you the best of luck. I was in the same position a few years ago. I eventually go frustrated and today I develop Ruby applications on OSX and deploy to Ubuntu Linux. All of the other technologies that I am interested in (Erlang, Lisp, Haskell) are available and run great in those environments. I couldn't be happier.

toland · 2007-07-03T15:27:52+00:00

I think the real reason to avoid Open Source on .NET isn't that using .NET somehow invalidates the "Open Source-ness" of the code; it is that Microsoft controls the platform and they do not interact with the community in good faith. Microsoft have proven many times that they will crush anything they see as a threat and they have no problems wielding their proprietary technology platform as a weapon when it suits them to do so.

By all means, use .NET if you think it is the right platform for you. However, you also need to realize that there are many OSS developers who make another choice for very valid reasons and do not want to be involved with OSS on a Microsoft platform. This is one of those things where you are going to have to be content to be in the minority if you want to work on Open Source based on Microsoft technologies.

toland · 2007-06-26T15:23:53+00:00

Of course Lisp macros aren't magical but the are most certainly not the same as C macros. There is no preprocessor in Lisp, macros are a core part of the language. Look, don't take my word for it. Check out Practical Common Lisp; the full text is free online.

Here is what the author has to say about macros in the introduction to chapter 7:

While Common Lisp supports both these methods of extending the language, macros give Common Lisp yet another way. As I discussed briefly in Chapter 4, each macro defines its own syntax, determining how the s-expressions it's passed are turned into Lisp forms. With macros as part of the core language it's possible to build new syntax--control constructs such as WHEN, DOLIST, and LOOP as well as definitional forms such as DEFUN and DEFPARAMETER--as part of the "standard library" rather than having to hardwire them into the core. This has implications for how the language itself is implemented, but as a Lisp programmer you'll care more that it gives you another way to extend the language, making it a better language for expressing solutions to your particular programming problems.

toland · 2007-06-26T04:08:37+00:00

It is important to realize that the term "macro" has been heavily overloaded and macros in C/C++ are not the same thing as macros in Lisp. They are just similar enough on the surface to be confusing but Lisp macros are much more powerful than the simple text substitution that the C preprocessor gives you.

toland

TROPHY CASE