Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 12 years ago.
Improve this question
Hey guys... Its quite late in the night right now and I'm taking some time off from coding my project. I discovered Coding Horror only a few weeks ago and I totally loved it. Having read all of its posts I have ran out of things to read when bored.
Can someone please suggest some great blogs (coding,computers) to read which are informative and fun one can read when bored?
This Site is great. I recommend :)
Something comedic?
Try Linux Hater's blog (http://linuxhaters.blogspot.com/).
Something educational?
Try Jon Skeet's coding blog (http://msmvps.com/blogs/jon_skeet/Default.aspx).
I browsed through my RSS feeds and grabbed out this selection.
Regular updates:
http://slashdot.org/ - Hopefully no
comment necessary. I read it for the
comments, not the articles.
http://thedailywtf.com/ - More for
the amusement factor than for any
self-improvement benefit.
http://blogs.msdn.com/b/oldnewthing/ - Often short updates, often technical, but I find I really enjoy
Raymond's blogging style.
http://www.paulgraham.com/articles.html - Not updated daily, but very interesting backlog of essays. Most
recent updates focus on venture
capital since that's where Paul works
these days, but earlier essays are
varied in focus.
http://martinfowler.com/bliki/ -
Similar to the previous one, sporadic
updates but entries are generally
well worth reading, especially if
you're interested in Agile
development.
Few or no updates, but great material to go through over time:
http://steve-yegge.blogspot.com/ -
Amusing (and long) "rants", generally
with a technology focus.
http://blogs.technet.com/b/markrussinovich/ - Interesting write-ups of technical problems and how they were solved
using SysInternal tools.
Windows-oriented.
reddit.com you will get hooked.
Steve Yegge's and Joel Spolsky's blogs have great stuff.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I know there is no clear answer to this question. I still wonder to know whether Reading open source code can improve myself rapidly? how and why?
ps：I keep reading open source code every day for months.
Well, many of the bigger open source projects are collaborations between many people: Thus you do have a chance of finding a project written by good developers, and therefore improve your own coding style. Of course, it all depends if you actually memorise the stuff you read or not - But I guess you wouldn't really read that much code if you didn't.
In my opinion, you can learn the following from well-written projects:
Coding conventions
Solutions to common problems (Of course, this depends heavily on the "type" of the project)
How to document code properly - If multiple people work on something, and the project is well-written, it probably also has a good documentation.
Of course, all of this is opinion-based, so you need to see for yourself.
Possible answers (this is highly subjective)
Because working with someone else's code is more difficult than working with my own code. It forces me to adapt to some else's thinking ("If all I have is a hammer, every problem looks like a nail")
Because open-source code is often not written under a deadline, by people who enjoy what they are working at, and can provide high-quality real-world examples
Because open-source code tends to have less of an agenda to push vendor XYZ's proprietary pet technology
Because the world might become a slighly better place, if people wouldn't code for the CPU as their main audience, but a human reader :)
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
in the past few weeks I have heard about a phenomenon called 'code-kata'. When I get it right, it means coding an exercise again and again. What is its point? Does it improve your abillity to design better software? If yes, why does it do so?
This was the first time I've heard of this, so after a quick google, here's my gut reaction:
Code Kata is not repeating an exercise over and over again. Rather it's about constantly expanding your "comfort zone" so you can grow as a developer.
Simply working on projects that you know how to do won't help you. You need to try and tackle projects that you would most likely fail at on your first attempt.
The end goal is that if you continuously try, fail, try again, fail again, etc, sooner or later you will succeed. When you do, you've mastered some new knowledge, and become a better developer.
Enough repetition of this will obviously improve your skill.
(Sorry if it's a bit of a brain dump)
I collected a bunch of references here: http://slott-softwarearchitect.blogspot.com/2009/08/code-kata-resources.html
The most important of these is http://codekata.pragprog.com/
It's not primarily to improve your design skills, rather it is a way to improve your productivity in your chosen IDE.
Repeating a familiar task over and over again allows you to watch out for and take advantage of IDE shortcuts and features that you were previously unaware of to shave seconds from your time. It will also help you find any unnecessary steps you take out of habit so you can cut them out of your routine.
We tried a few of these at my company, our thoughts were to develop a simple game (obviously something with a bit of logic we'd not know how to do). We'd all have a go at doing it, then we'd keep improving it as much as we could until we thought we had the best way to do things, then we'd meet up again maybe a week later and compare our results. It's interesting to see how different people come up with different solutions, and everyone learns from the experience. Maybe not a proper kata, but we always try and bend these things to something we'd find useful :)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
Cofundos is a project where you can pay for tasks to be completed in open-source programs. If a developer solves this task, he will earn the money. Is this a good way to push open-source software?
No.
Joel Spolsky has talked about the phenomenon of people doing for free what they would never do for pay in the context of contributing to sites like Stack Overflow. People have all sorts of reasons for doing things for free:
Helping out a friend or society.
Fame and recognition.
Hobby or passtime.
Building a resume.
Learning about the world around them.
When you offer money it either destroys the purpose of doing something ("It's not a hobby if I get paid—it's a job.") or reduces the intrinsic value of doing it ("I'm not helping out society—I'm helping out me."). The same is true for Open Source contributions.
People do get paid for Open Source work. But normally by companies who are using Open Source software and need certain features and fixes. Sometimes they are full time, but often it's just submitting a bug fix or feature so that it will be carried to the next release. But that happens because the project is useful to the company.
So a better way to "push" Open Source is to use Open Source. If a project is missing a feature, you'll need to add it yourself or find someone else who will. Any scheme that offers money for a feature directly will likely not work. And if the feature does get added, it'll be added by someone who wants to get paid rather than someone who wants better software.
Well if you absolutely need a new feature in a program and you can't contribute, then sure. Otherwise I don't see why you don't just do it. You'll learn more by doing it yourself.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I always have found the open source space interesting but have never actually participated in any projects. I recently had what I thought was a great a idea that was different from other projects I had seen in the area (in case it matters it was a .NET DI framework).
My question is if I have a funky idea should I join an existing project and share my ideas or create a competing project with exactly what I want. There are a few projects in the space the are similar to what I was thinking but they don't quite capture the same ideals.
Is extra competition frown upon in the open source space?
Competition is as important as collaboration in open source. Assuming the licenses are compatible, features and ideas can be cross-pollenating. Everybody wins.
the short answer to this is another question: do you want to contribute to a discussion, or do things your way?
You may want to consider writing it your own way and turning that process into an article that you could submit to CodeProject. Then if there seems to be interest in the article, add it to SourceForge. I've seen a lot of tools and widgets get a quick audience and coding help that way. One that I use often is XPTable, which started as a CodeProject article and eventually became an open source project on SourceForge.
BTW, you'll know if its a hit, because you'll start to get lots of requests for improvement, or people even submitting their own fixes and enhancements to your article.
Thank you for your time. I have decided to contribute directly for the project in some areas they were hurting. By doing so I can help the project and learn from the masters.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
What open source projects would you recommend as a good place for a starting open source developer? Factors that I think would be important are some obvious ones like well written code and a community that is helpful to newbies. But it might be nice if the code base is such that I can start hacking some small problems without really understanding the details of how everything works.
I'd prefer something that can be developed on Linux using C/C++/Java/Python/Scala.
Trying to pick a project like that will never work because it's not something you're passionate about. What's an open source project that you use daily or enjoy using? Go work with that one.
It really depends on what your interests are as to what project to dive into.
Rationale for a larger project (e.g. Firefox, OpenOffice, etc) is that it has many developers, a well established code base, and many small tasks/bugs to be worked out.
Rationale for a smaller project is that you will become more intimate with the code and application. You will likely get to know other developers on the team and understand the overall concept better. Additionally, your additions to the project may be more noticeable.
sourceforge has a list of projects seeking a new developer. Therer are several for your requested programming languages:
http://sourceforge.net/people/?category_id=1
Apart from developers they have more help requests:
http://sourceforge.net/people/
Pick one you use and like already.