Design patterns are reusable solutions to commonly occurring problems in software design. They are both exciting and a fascinating topic to explore in any programming language.
One reason for this is that they help us build upon the combined experience of many developers that came before us and ensure we structure our code in an optimized way, meeting the needs of problems we’re attempting to solve.
Design patterns also provide us a common vocabulary to describe solutions. This can be significantly simpler than describing syntax and semantics when we’re attempting to convey a way of structuring a solution in code form to others.
Book is also available to download and fork on GitHub
Words that I definitely subscribe to:
As a programmer in the U.S. for 30 years now I have spent some of that time working more than 40 hours in a week, which is not all that common in this industry, and when I was salaried I rarely if ever got more pay.
No more, I now find the whole idea nauseating.
Sometimes when I go out to eat, I will keep score on the waiter’s or waitress’s performance. They start out with a baseline of 10% and can earn or lose 1% at a time for extra good or poor service.
Today the waitress finished with 6%. Nothing remarkable happened that might have earned her extra percentage points. And she did four things to lose points:
No matter what type of service you are trying to provide to your client, it is often the very small details that can end up creating a positive or negative impression (and can often end up costing you).
Good (if long) article describing the common denominators among the different nosql platforms, how the needs of database consumers (both on the developer and on the client levels) have changed over time to make today’s environment one where a RBDMS might not be what is needed.
There was a tragic bus accident this morning near Jerusalem — a Palestinian school bus hit a truck, causing the bus to flip over and catch on fire. The Palestinian Red Crescent hasn’t made up its mind yet about the number of casualties, but between 6-8 children were killed and dozens injured — some seriously.
Yet immediately after the tragedy, the Palestinian Authority’s Health Minister, Dr. Fathi Abu Morley called a press conference in Ramallah, blasting Israel for “not responding in time”
The Palestinian’s lie is simply and absolutely disgusting.
As a first responder medic for both Magen David Adom and United Hatzalah emergency response medical services, I received a MDA emergency pager message at 9:13 AM this morning, that a school bus had flipped over and a mass casualty incident was declared. Moments later I received an SMS from United Hatzalah, calling on all emergency medical personnel in the area to respond. I switched to channel 1 on my United Hatzalah cellular radio, and heard dozens of first responders announcing they were on their way to the scene of the accident. No one even mentioned that it was a “Palestinian school bus” — since that was completely irrelevant.
Syrian guns can obliterate a field hospital; leave the wounded bleeding to death in the streets; and rampage through hospitals shooting rebel troops, while the world merely clicks its tongue in disapproval. But if Israel tries to move 25 Palestinian squatters from a shanty village they set up in a Jerusalem national park, the global protests will be loud and vociferous.
One selected review:
As a Fertility Specialist for Pachyderms, this was exactly what we needed to help rebuild elephant populations all over sub-saharan africa. It’s not all just Medications and IVF treatments. Some times you need a loudspeaker, a Barry White CD and a 55 Gallon drum of Lube.
What we found over time was that there is a lot of really good talent in that pool, which the industry had overlooked. Based on a few years of observation, we noticed that there was little or no correlation between academic performance, as measured by grades & the type of college a person attended, and their real on-the-job performance. That was a genuine surprise, particularly for me, as I grew up thinking grades really mattered
Atwood leaves StackExchange … Coding Horror is resurected?
Although some meetings are inevitable, even necessary, the principle he’s advocating here is an important one. Meetings should be viewed skeptically from the outset, as risks to productivity. We have meetings because we think we need them, but all too often, meetings are where work ends up going to die. I have a handful of principles that I employ to keep my meetings useful:
- No meeting should ever be more than an hour, under penalty of death.
The first and most important constraint on any meeting is the most precious imaginable resource at any company: time. If you can’t fit your meeting in about an hour, there is something deeply wrong with it, and you should fix that first. Either it involves too many people, the scope of the meeting is too broad, or there’s a general lack of focus necessary to keep the meeting on track. I challenge anyone to remember anything that happens in a multi-hour meeting. When all else fails, please keep it short!…