J of K
The article can now be found at http://clicktobegin.net/programming/why-you-shouldnt-use-dev-c/
Please update any bookmarks.
I'm planning a follow-up entry discussing the merits of using an updated version of Dev-C++, as I've recently seen a bit more awareness of wxDev-C++ and the much newer Orwell Dev-C++.
Facebook can be a great way to connect with people and keep in touch. However, by default Facebook generates a lot of notifications, both via it’s own interface and by email, often about a lot of things you might not care about. There are however a few things you can do to manage and reduce the traffic so that you see less of the junk, and hopefully more of what interests you. If you have a couple of spare minutes and would like to try removing a lot of the annoyances that come along with Facebook you might consider some or all of the following simple suggestions:
1. Filter your news feed to show status updates only.
The news feed is what you see by default on your Facebook homepage when logged in. It contains status updates, recently posted photos or links, new notes and a wide assortment of traffic generated by Facebook applications your friends use. Many people would prefer to see less of the other (sometimes annoying, particularly in the case of some applications) content and just see status updates in this section, and it’s quite easy to do so.
Full post at Unrefined Awesome...
To give a couple of examples of recent editions I'll link to the June Help Wanted Picks, and the July edition; this month I made the experimental adjustment of seperating out "services offered" into a seperate edition posted in the middle of the month.
Why am I posting this?
I'd like feedback on what I'm doing. Anyone who has been following the column will see that I've been making changes each time trying to find out how best to provide a useful piece that people will actually value. In particular, there's some discussion in the comments of the latest 'Help Offered Picks' that I'd like additional feedback on, and any other comments on the column (either version) in general are most welcome.
What do you want to see in the Help Wanted/Offered Picks?
The first reason is fairly obvious. Most people looking for a project to join have the same few generic questions regarding things such as payment, choice of technology and the goals of the project. The various sections of the template provide the majority of that information, saving people the need to ask and allowing people to quickly glance over the sections that most interest them.
The second reason can be somewhat less obvious however. Having to fill out the template forces people to think about those details of their project, and (although this doesn't seem terribly effective) it is hoped that in at least some cases will encourage people to do a little more preparation before forming a team. The majority of sections are things that any well thought out project should be able to answer without any problems, and apart from those headings marked as optional it should probably raise warning-flags if you're having trouble coming up with answers to any of them.
Thirdly, a poorly filled out template can often be a quick indicator to experienced users browsing the threads that a project probably doesn't have good chances.
Look at for an entry in the next few days on potential alterations to the current template.
There's a well-known document called How To Ask Questions The Smart Way that a lot of forums, newsgroups and faqs link to as an explanation of how to approach seeking help. It’s well written, comprehensive and gives a very good explanation of how and why people should improve their questions. However, it's also really long, makes frequent use of the term "hacker" (which to the majority of people in need of help with asking questions has a meaning other than what is intended) and in my opinion is probably a little too long winded and a bit out of touch with many (but not all!) modern programming fora and newgroups. The following is my attempt at a more concise version without some of the dated jargon or opinions that may not be relevant to some communities.
Read the rest of the entry at Unrefined Awesome.
from Why you shouldn't use Dev-C++
I still see a lot of people using the out-of-date and unmaintained Bloodshed Dev-C++ IDE (Integrated Development Environment), and I’d like to briefly explain why this is a bad idea as well as pointing any interested readers toward a couple of good alternatives.
Read the full post at Unrefined Awesome.
from Why you shouldn't use Visual C++ 6
In the same vein as my earlier post on Why You Shouldn't Use Dev-C++ I'd like to outline a few reasons you shouldn’t still be using Visual C++ 6.0. These arguments may not apply if you’re working with a computer that is both particularly underpowered and running a very old (pre-’98) version of Windows, but in the overwhelming majority of cases VC++6 is a terrible choice of development environment.
Read the full post at Unrefined Awesome.
Check it out and let me know if you've got any more feedback.
I also got the suggestion last time of highlighting one bad post as an example of how not to do it. While this would be both educational and potentially amusing I don't feel it's really in the spirit of encouraging beginners (even if they're really bad now they might get better with some prompting), and doesn't seem overly professional. As an alternative however, would people be interested in seeing short snippets giving tips on succesfully recruiting from some of our current and/or previous users?