How I failed: Six lessons learned. Wonderful set of insights from Tim O’Reilly. Number four is a very hard problem to solve.
Effective Technical Leadership. Rich with usable attributes and actions.
Couple of things I learned the hard way yesterday:
- When using a password to connect to an IRC server, you’ll need to join the room before you can post a message to it.
- IRC servers (or maybe it’s just ours) are quite slow to fully respond to connection requests. Like, two minutes slow.
Advantages of pre-deploy code review, over post-deploy audit: Authors have a strong incentive to craft small, well-formed changes that will be readily understood, to explain them adequately, and to provide appropriate test plans, test coverage and context. Reviewers have a real opportunity to make significant… Continue reading →
I like to think of funded startups vs. bootstrapped web sites like the split between signed and unsigned bands.
Think about what a band has to do if they sign with a major label. They write music, perform/record it, and play it. Now think about people like Prince, Aimee Mann, etc. that do every single aspect of their music themselves. They have to create and record and distribute music, but also book tours and hotels and hire roadies and even oversee building websites. On the positive side, those going their own way talk about making more money from lower record sales than they did on a label, even though they do a significant amount of work.
So it’s a lot of work, but I would argue it’s totally appropriate for anything that isn’t a huge world-changing idea. And there are a lot of benefits that come from it.
Writing beginner level tutorials. A number of useful tips. My favorite: “use words and phrases that your reader can Google to find more information.” For producers of documentation, I think the biggest challenge is putting yourself in the mindset of the reader. The second biggest challenge is closing the feedback loop between the person who has the knowledge and the person who wants the knowledge.
Today we differentiate between blogging on blogging platforms and sharing on social platforms, but that is just semantics. The essence of blogging is not defined by a platform but by what I learned from Dave and his blogging platform — that media now is raw,… Continue reading →
Meet wpshell – the power of WordPress at your prompt. wpshell is an undiscovered gem. Someone should lead a WordCamp talk about it and the secrets it holds.
In other words, my theory is: Cheating (on a systematic level) happens because students try to get an edge over their peers/competitors. Even top-notch students cheat, in order to ensure a perfect grade. Fighting cheating is not something that professors can do well in the long run, and it is counterproductive by itself. By channeling this competitive energy into creative activities, in which you cannot cheat, everyone is better off.
Panos Ipeirotis — Why I will never pursue cheating again. A computer scientist teaching in a business school details a year of trying to combat cheating on assignments. Overall, he spent 45 hours addressing the problem during a 32 hour lecture course, and 22 of 108 enrolled students admitted cheating. Solutions could include:
- Public projects – All of the work ends up public, so embarrassment is the deterring factor.
- Peer review – Students have to present their work in class, and are judged by others.
- Competitions – Grades are performance-based (e.g. students build websites to attract the greatest number of unique visitors).
Takeaway: If plagiarism is your biggest worry, you’re doing it wrong.