> Not be self-promotional, but as a hobby... I think you meant, "Self-promotion: As a hobby...". And that's just fine, I for one appreciate it.
Perl doesn't have real macros. It has a pretty neat, get you most of the way there aftermarket bolt on. Kind of like its object system. Similarly, you can do a lot with it. But it ain't Lisp macros.
>in other languages there seems to be much more consensus about what features one should use, how and when Especially in theory. Python so desperately wants to not be Perl in this regard, so much that they codified…
Reliable transport is a hard problem, and a problem that TCP does a good job of. I have to add ACKs to my application layer if I write code atop telehash when I care about delivery of my datagrams? That gets hairy, real…
except the one thing you'd like to argue with. It's the part of your comment I think is crazy. Of course I'm going to comment on that in particular. I believe you mean, "I don't understand how that could be the case."…
... if you have a bunch of individuals doing great programming that doesn't add up to a functioning project. That's impossible.
So as far as I can tell, what you're saying is that it's impossible to take any process ideas from an external source, because every team is already maximally efficient. Nope. I'm saying that the process of programming…
I had to remove the font-family: 'PT Sans' declaration from your site's CSS using Chrome's element inspector in order to read it. Chrome 16.0.912.77 on Fedora 16 here. I believe PT Sans is a readable Russian language…
So many people date in NYC, so few commit for the rest of their lives. You just made that up.
Either way, it's nothing to get worked up over. Oh, I agree. My language was for emphasis, not representative of an emotional state. It's interesting to talk to someone who thinks that the same process can save a bad…
A 15-minute standup isn't going to hurt a good team's productivity, while it could greatly improve the productivity of a mediocre team. It takes a lot to noticeably hurt a good team's productivity. But it's mean, just…
"Good enough" is certainly better than "not good enough". In the scenario that you described, someone went from not communicating at all to lying every day, and getting "caught" at the end of a sprint. Standups didn't…
"Sure it can... If he lies every day about what he does, the longest he can go is one sprint before his work gets verified." That's not fixing bad communication. That's wrapping it up in process, and calling it "good…
You say "techniques of effective collaboration", I say "talking to people". If you need guidelines for that, that's cool. The thing that suggests to me that you and I wouldn't work well together is that you make broad…
No amount of process can fix bad communication. Standups are an attempt at that. Teams that have good communication succeed more, and standups aren't integral to their success. Teams with bad communication fail more,…
That's right. It means slower software. That's not what Agile consultants are selling.
I meant to answer your original question, but HN decided I couldn't post any more under "itsnotme". "So how do you build things that take thousands of programming hours to complete?" By programming for thousands of…
Processes implemented to save lives are the product of death, and the process is put there to slow things down. Ask your friendly agile consultant how much their process is going to slow down your company. They will…
HN's algorighm thinks I'm a spammer and wouldn't let me reply, but really, itsnotme. I could collaborate well with that person. If I like the product and the people enough I'll work on a team that uses "Agile". But I do…
> Not be self-promotional, but as a hobby... I think you meant, "Self-promotion: As a hobby...". And that's just fine, I for one appreciate it.
Perl doesn't have real macros. It has a pretty neat, get you most of the way there aftermarket bolt on. Kind of like its object system. Similarly, you can do a lot with it. But it ain't Lisp macros.
>in other languages there seems to be much more consensus about what features one should use, how and when Especially in theory. Python so desperately wants to not be Perl in this regard, so much that they codified…
Reliable transport is a hard problem, and a problem that TCP does a good job of. I have to add ACKs to my application layer if I write code atop telehash when I care about delivery of my datagrams? That gets hairy, real…
except the one thing you'd like to argue with. It's the part of your comment I think is crazy. Of course I'm going to comment on that in particular. I believe you mean, "I don't understand how that could be the case."…
... if you have a bunch of individuals doing great programming that doesn't add up to a functioning project. That's impossible.
So as far as I can tell, what you're saying is that it's impossible to take any process ideas from an external source, because every team is already maximally efficient. Nope. I'm saying that the process of programming…
I had to remove the font-family: 'PT Sans' declaration from your site's CSS using Chrome's element inspector in order to read it. Chrome 16.0.912.77 on Fedora 16 here. I believe PT Sans is a readable Russian language…
So many people date in NYC, so few commit for the rest of their lives. You just made that up.
Either way, it's nothing to get worked up over. Oh, I agree. My language was for emphasis, not representative of an emotional state. It's interesting to talk to someone who thinks that the same process can save a bad…
A 15-minute standup isn't going to hurt a good team's productivity, while it could greatly improve the productivity of a mediocre team. It takes a lot to noticeably hurt a good team's productivity. But it's mean, just…
"Good enough" is certainly better than "not good enough". In the scenario that you described, someone went from not communicating at all to lying every day, and getting "caught" at the end of a sprint. Standups didn't…
"Sure it can... If he lies every day about what he does, the longest he can go is one sprint before his work gets verified." That's not fixing bad communication. That's wrapping it up in process, and calling it "good…
You say "techniques of effective collaboration", I say "talking to people". If you need guidelines for that, that's cool. The thing that suggests to me that you and I wouldn't work well together is that you make broad…
No amount of process can fix bad communication. Standups are an attempt at that. Teams that have good communication succeed more, and standups aren't integral to their success. Teams with bad communication fail more,…
That's right. It means slower software. That's not what Agile consultants are selling.
I meant to answer your original question, but HN decided I couldn't post any more under "itsnotme". "So how do you build things that take thousands of programming hours to complete?" By programming for thousands of…
Processes implemented to save lives are the product of death, and the process is put there to slow things down. Ask your friendly agile consultant how much their process is going to slow down your company. They will…
HN's algorighm thinks I'm a spammer and wouldn't let me reply, but really, itsnotme. I could collaborate well with that person. If I like the product and the people enough I'll work on a team that uses "Agile". But I do…