I recently re-read Martin Fowler's excellent book on refactoring. It's about improving the design and quality of your code in small steps, without changing external behavior. The book contains detailed descriptions of refactorings, with motivation, mechanics, and an example for each. A must-read.

By June 1949, people had begun to realize that it was not so easy to get a program right as had at one time appeared. It was on one of my journeys between the EDSAC room and the punching equipment that the realization came over me with full force that a good part of the remainder of my life was going to be spent in finding errors in my own programs. — Maurice Wilkes, creator of the first stored-program computer, EDSAC Debugging is programming, and programming is often mostly debugging. One of t

Weddings are an occasion for gift giving, and a fine watch always makes an ideal gift, whether it’s from a parent to a prospective son- or daughter-in-law, a groom to a best man, or exchanged between the betrothed couple in addition to (or in place of) the traditional rings. What are the best wedding watches? We put th

None

None

The software industry is learning once again that complexity kills

Those new to functional programming often wonder when to use higher-order functions (or blocks/procs/lambdas in Ruby). I did, too. In this post, we'll implement the map method from scratch, in turn gaining an intuitive understanding of higher-order functions and when to use them.

An educational puzzle game. Solve a series of tasks where you build increasingly powerful components. Starts with the simplest logical components and ends up with a programmable computer.

Become a computer operating system and try not to anger the user!

Tutorials for Raspberry Pi ⚫ Projects and Applications for Beginners and Experts ⚫ Raspberry Pi First Steps ⚫ and many other RasPi Tutorials.

Learn about the Jews of Curaçao: their rich history, magnificent synagogues, historic cemeteries, fascinating museums, and other delightful other sites. Find everything you need to plan a visit. CuracaoJews.org is an initiative of the Jewish Cultural Historical Museum as we approach 400 years of Jewish life recorded on the island of Curaçao.

null

Simple.css is a classless CSS template that allows you to make a good looking website really quickly. - kevquirk/simple.css

agoodmovietowatch is the world’s first portal of highly-rated but little-known movies and shows. Curated by humans and not algorithms.

With over 10 million hours of instruction provided since 2005, Wyzant.com is the nation's largest marketplace for in-person...

Search Google, YouTube, Instagram, TikTok, Twitter, Reddit, Amazon, Images, News, & more. See all results by swiping — no clicking.

Syllabi Policies for AI Generative Tools If you would like to submit your course guidelines/policy to be included here, please submit it in this form. Update: If you would like a more searchable version of this document, try out this spreadsheet that allows you to sort by Course, Discipline...

The telephone, invented by Alexander Graham Bell in 1876, sparked a revolution in communication. A year later, in 1877, he established the Bell Telephone Company. This marked the beginning of a fascinating journey, leading to the formation of the Volta Bureau in 1880. Guided by Bell, the Volta Bureau became a research hub, making strides in multiple scientific fields.

The great thing about measuring developer productivity is that you can quickly identify the bad programmers. I want to tell you about the worst programmer I know, and why I fought to keep him in the team.

In software engineering organizations, there are certain practices that keep costs under control even if those seem more expensive at first. Unfortunately, because such practices feel more expensive, teams choose to keep their status quo even when they know it is suboptimal. This choice ends up hurting productivity and morale because planned work is continuously interrupted, which in turn drags project completion.
The reason I say seem and not are is because the alternatives to these cost-exposing practices also suffer from costs. The difference is that, while the former surface costs, leading to the need to allocate time and people to infrastructure work, the latter keeps the costs smeared over teams and individuals in ways that are difficult to account and plan for.
To illustrate what I’m trying to say, I’ll present three different scenarios in which this opinion applies. All of these case studies come from past personal experiences while working in different teams and projects. The first one covered in this post is about the adoption of a monorepo vs. the use of multiple different repositories. The other two will come in follow-up articles.