16 bookmarks for 2024-05-17

A properly configured distributed team of programmers can and must deliver a higher quality of code than a co-located one.

658.

Paying by the hour is a modern form of slavery that must be replaced by paying for results, which is a much more effective and healthy form of management.

657.

How do you know what hourly rate you are worth? What factors should be taken into account? Here are my criteria.

656.

Equity or cash? These days, it seems that working for equity is the way to become a millionaire. I don't think it's true.

655.

I often hear the question of how to become a senior developer; this is my story and my advice; hope it helps you.

652.

If you actively use Stack Overflow as a coding instrument, your reputation will be lofty; if you don't use it, you're not really a professional software engineer.

651.

Twenty years ago we worried about performance. Now it is time to worry about maintainability, even though it often compromises performance.

650.

When a task you're working on is too big or you simply don't want to do it, you cut corners; here is how you can do it professionally.

649.

A project is not a school, and it shouldn't pay for our education; however, we want to learn while working on a project. Here is some simple advice on how to align our goals and project objectives.

648.

An active open source contribution is a good habit for a software developer who is passionate about his or her job.

647.

Chats, emails, phone calls, mailing lists, issue tracking systems, face-to-face meetings, and other communication instruments for a software project.

646.

In XDSD everybody is motivated to produce tangible and meaningful results. That's why we don't use emails, Skype, HipChat or phone calls.

645.

Patent-pending methodology of breaking down big tasks into smaller ones is explained in the article, by example in Java

644.

Micro-tasking is a management paradigm we've been practicing for over eight years, to the benefit of our programmers and project sponsors.

643.

Solving technical problems in a large scope which is difficult to understand is a very stressful activity; I suggest we behave professionally.

642.

Programmers are expensive and difficult to control; here are a few tricks to keep them underpaid and happy, for a while.

641.