Why programming methodologies are pointless
l8d.github.io
Why programming methodologies are pointless
1–10 of 28 posts
Re: Why programming methodologies are pointless
#2ಠ_ಠ
Re: Why programming methodologies are pointless
#3"To anyone who has moderate experience in software development, this might seem obvious or taken for granite " ಠ_ಠ
Make my words, when you get down to brass stacks it doesn't take rocket appliances to get two birds stoned at once. It's clear who makes the pants in this relationship, and sometimes you just have to swallow your prize and accept the facts. You might have to come to this conclusion through denial and error but I swear on my mother's mating name that when you put the petal to the medal you will pass with flying carpets like it’s a peach of cake.
Re: Why programming methodologies are pointless
#4Re: Why programming methodologies are pointless
#5"To anyone who has moderate experience in software development, this might seem obvious or taken for granite " ಠ_ಠ
Re: Why programming methodologies are pointless
#6"To anyone who has moderate experience in software development, this might seem obvious or taken for granite " ಠ_ಠ
Re: Why programming methodologies are pointless
#7I like to call this the 'fallacy of assumed competence'. We assume teachers are good at teaching, and teachers assume students are good at learning and understanding. As i've grown older i've come to believe that most teachers suck really hard at teaching, and that most students suck really hard at knowing how to ask the teacher what they need to know.
In terms of programmer methodologies: nobody in the real world cares all that much. Nobody quits their job because their bosses wouldn't enforce using their preferred methodology. If you're all tasked with developing some giant framework or application and you all have to work together, at some point you learn it's a lot less painful to put your ego aside and just get work done.
Re: Why programming methodologies are pointless
#8Having a desk job helps in understanding it is more important that you can understand your code 3 years down the road than squeeze the last 5% of productivity out right now.
Re: Why programming methodologies are pointless
#9"To anyone who has moderate experience in software development, this might seem obvious or taken for granite " ಠ_ಠ
Allow me to play doubles advocate here for a moment. For all intensive purposes I think you are wrong. In an age where false morals are a diamond dozen, true virtues are a blessing in the skies. We often put our false morality on a petal stool like a bunch of pre-Madonnas, but you all seem to be taking something very valuable for granite. So I ask of you to mustard up all the strength you can because it is a doggy do…
Re: Why programming methodologies are pointless
#10This looks to be the crux of your argument and it's a weak one. Just because there are wide ranging opinions on definitions does not mean the ideas have no merit. The idea of "education" means something very different to many people. That doesn't mean that public school, college, or Cisco certification training is "pointless". There are thousands of ideas/words that don't meet 100% agreement. Just the other day, there was a thread on HN about what "mathematical proof" meant. Does that mean someone can legitimately dismiss math proofs as pointless because mathematicians disagree?
Alan Kay's idea of "object-oriented" is different from Bjarne Stroustrup's. Martin Odersky's idea of "functional language" is different from John McCarthy's. Regardless of the differences, there are still good ideas in both OOP and functional paradigms that can improve designs of software architectures.
>I don’t know if I should “love to hear your argument against this” but since this is a blog post from some obscure programmer on the internet, then I’m sure you’ll write it anyways.
I don't understand the conceit you wrote here. If this is how you truly felt, why did you post your blog to HN? I thought the idea was to invite commentary.