Group items tagged

Certainly true for me in a variety of areas of learning . . . "Programming was taught to me in a similar way - and for students to attain true understanding, this doesn't feel like it's the best way to learn. There is a literal learning curve to programming, and once you hit the inflection point of that curve you become somewhat self reliant. You know what to ask Google, you know the process of debugging, and you start to realize you're capable of accomplishing anything by yourself. But if you haven't hit that point yet, it can feel like you may never hit that point. Traditional methods of testing and gauging progress among students who are at different points in their capacity to learn programming don't feel quite fair, and I believe this discourages many (particularly underrepresented minorities) from continuing to learn how to code."

Certainly true for me in a variety of areas of learning . . . "Programming was taught to me in a similar way - and for students to attain true understanding, this doesn't feel like it's the best way to learn. There is a literal learning curve to programming, and once you hit the inflection point of that curve you become somewhat self reliant. You know what to ask Google, you know the process of debugging, and you start to realize you're capable of accomplishing anything by yourself. But if you haven't hit that point yet, it can feel like you may never hit that point. Traditional methods of testing and gauging progress among students who are at different points in their capacity to learn programming don't feel quite fair, and I believe this discourages many (particularly underrepresented minorities) from continuing to learn how to code."

I/we need to consider this with our team and education more broadly. "Theory 1: Nothing we "know" about software development should be assumed to be true. Most of our tools, our mental models, and our practices are remnants of an era (possibly fictional) where software was written by solo practitioners, but modern software is a team sport. Theory 2: Technology is the product of the culture that builds it. Great technology is the product of a great culture. Culture gives us the ability to act in a loosely coupled way; it allows us to pursue a diversity of tactics. Uncertainty is the mind-killer and culture creates certainty in the face of the yawning shapeless void of possible solutions that is software engineering. Culture is what you do, not what you say. It starts at the top. It affects everything. You have a choice about the culture you promote, not about the culture you have. Theory 3: Software development should be thought of as a cycle of continual learning and improvement rather a progression from start to finish, or a search for correctness. If you aren't shipping, you aren't learning. If it slows down shipping, it probably isn't worth it. Maturity is knowing when to make the trade off and when not to. I had some experience with this at Flickr, and I wanted to see how far you could scale it. My private bet was that we'd make it to 50 engineers before things broke down. Theory 4: You build a culture of learning by optimizing globally not locally. Your improvement, over time, as a team, with shared tools, practices and beliefs is more important than individual pockets of brilliance. And more satisfying. Theory 5: If you want to build for the long term, the only guarantee is change. Invest in your people and your ability to ask questions, not your current answers. Your current answers are wrong, or they will be soon. "

On the function side, Google intends to make the news as balanced and objective as possible with options including comparisons of the same story from multiple, competing news sources, news only from eyewitnesses, and a graphic coverage timeline to track the progress of reporting as well as the events of the story.

" also share a lot of your concerns about specifics, but I think I've found a way to work my brain around it. You're absolute right; we've been conditioned to think in terms of exact numbers. We're used to being told our posts should be 200 words with 4 paragraphs and exactly 8 links to external sources, so that's how we've learned to function. I think this class has been great for me to retrain my brain to think creatively rather than within the confines of instructions. For length, I just make sure I answer the question. I ask myself if I feel that my answer is appropriate, or if I should go into more detail. It helps me if I stop focusing on the grade (as hard as that is) and instead focus on the assignment itself. If I can answer the question with detail in two sentences, I feel like two sentences is a perfectly fine entry. Most of the time, my entries are 2-3 paragraphs. I just write down what I'm thinking, rather than trying to filter through "Is this what Dr. Becker wants to see?" I think my work looks a lot better when I'm focused on what I think looks respectable, rather than trying to mold myself to what I think others may expect of me." h/t Jon

"So give me an A-, because my dreams overshot my constraints, and my vision for the final project didn’t come in on time. But I came to class prepared for every discussion, and led it in fact. I read every assigned reading, and listened to the commentary of my classmates. I did the blogs that were required, and I wrote every paper on time and with gusto. I stopped wasting my time and I stopped wasting the classes time, of which I am also proud. And I opened myself to the possibility that I am wrong sometimes, which unbelievably only took me 22 years. I want an A, and I believe I just explained why I deserve as much. But I realize only after having done the work required to become an A thinker how little an A really means to me, and how much better I feel knowing that."

"Not Just On the Web but Of the Web" Excellent, accessible discussion about making web content unique to its platform, using mainstream (NPR) examples.

h/t David C.

I could have written this (absent email arguments). "I could have written that yesterday. I've learned a ton more about programming and databases; I've spent time getting the basics of computer science; and it's all to just keep doing the same damn things over and over again, and then forgetting I did them, and repeating them. Like a version of Groundhog Day about making Groundhog Day. "