... for trying to achieve /what/ excactly?
Nuance. I know. Nuance is overrated. Especially on the interwebs. Sorry about that.
61–70 of 73 posts
... for trying to achieve /what/ excactly?
Nuance. I know. Nuance is overrated. Especially on the interwebs. Sorry about that.
Earlier quoted context omitted.
This is commonly known as cheating. I'm fairly confident it doesn't happen very much.
I'm pretty sure you're talking about some game, not hackathons.
We just had a very successful hackathon where I work. About 10 separate teams coded basically overnight and the results I think surprised everybody. There was something about the energy and, well, slight insanity of staying up all night just to see if we could deliver a full product in under 20 hours...there was definitely something to it. The demo the next morning, where all the teams showed what they had done was p…
Hackathons are not the nonsense in this piece, the author's assumption that hackathon projects are expected to be actual business-ready products, that's the nonsense. The author is really shooting himself in the foot and missing the point of hackathons: they are about experimentation and practice. > However, to make good software, requires lots of thought, trial and error, evaluation, iteration, trying the ideas out…
My feet are just fine, btw. :-)
Why 24 hours? I find that I need to clear my mind after four or five hours of technical work. If I do that, I get a lot more done.
And my projects come in 4-5 hour chunks of code writing and debugging and everything else that goes into the development process. A bit, but actually very little, requires or even benefits from face to face talking with people. The level of concentration required is blown by just one conversation.
Why not other structures for collaborative development?
I like taking one-hour walks with people I'm working with. Lots reason this works really well.
Demos are good too -- for sure. I could see a meetup where people got together to do one-on-one demos of projects they're currently working on.
I suspect that's what people are really doing btw at hackathons. :-)
If you go back and look at my piece and read the first sentence, you might get an idea of how I approached this.
It was just a blog post, btw, not a manifesto!
People here are reading way too much into it.
Hackathons are not the nonsense in this piece, the author's assumption that hackathon projects are expected to be actual business-ready products, that's the nonsense. The author is really shooting himself in the foot and missing the point of hackathons: they are about experimentation and practice. > However, to make good software, requires lots of thought, trial and error, evaluation, iteration, trying the ideas out…
Where did you get the idea that that was my assumption? My feet are just fine, btw. :-)
Let me ask you guys a questions, the people who say that Hackathons are great. Why 24 hours? I find that I need to clear my mind after four or five hours of technical work. If I do that, I get a lot more done. And my projects come in 4-5 hour chunks of code writing and debugging and everything else that goes into the development process. A bit, but actually very little, requires or even benefits from face to face tal…
Let me ask you guys a questions, the people who say that Hackathons are great. Why 24 hours? I find that I need to clear my mind after four or five hours of technical work. If I do that, I get a lot more done. And my projects come in 4-5 hour chunks of code writing and debugging and everything else that goes into the development process. A bit, but actually very little, requires or even benefits from face to face tal…
> People here are reading way too much into it.
You are Dave Winer. How can you expect people to not read into it, especially one with such a provocative title?Let me ask you guys a questions, the people who say that Hackathons are great. Why 24 hours? I find that I need to clear my mind after four or five hours of technical work. If I do that, I get a lot more done. And my projects come in 4-5 hour chunks of code writing and debugging and everything else that goes into the development process. A bit, but actually very little, requires or even benefits from face to face tal…
> People here are reading way too much into it. You are Dave Winer. How can you expect people to not read into it, especially one with such a provocative title?
Who said I didn't expect them to do it!
Of course they're going to do it.
And of course I'm going to say they're doing it.
And of course someone is going to ask how can you expect people to not read into it, especially one with such a provocative title?
Conclusion: Life is wonderful!! :-)
No sarcasm, this is fun.
Earlier quoted context omitted.
as a regular long run runner and coder, I totally agree with you. For training, not only building base is important, if you wanna achieve a good pace during marathon, running fast like a blast is part of it. More detailed, we basically have 4 phases for training. 1)acclimatizing phase, 2)building-up phase, 3)overall preparation phase, and 4)special preparation phase. Hacktons are more like phase 4, not so accurate an…
Hackathons are more like fartleks, no?