Author: admin

Our attendance at the recent Sima-Asean Agribusiness trade show in Bangkok confirmed that the farmers really loved their late king – King Bhumibol Adulyadej now known as King Rama IX. At the exhibit booth of the farmers’ cooperative, the portrait of the late king was prominently displayed.
Of course it is easy to understand why. We personally know that King Rama IX in his long reign as monarch, had helped farmers cooperatives in a big way. For instance, the biggest dairy co-op in Thailand, the Nong Pho Dairy Cooperative, has been under Royal Patronage. The king himself had put up about half of the capitalization of the cooperative that had a revenue of 1.7 billion baht during our visit some five years ago. He received annual dividends but we were told that he gave that to the co-op for the scholarship of the farmers’ children as well as for research and development (R&D) and extension services.

Source: The reason why the Thais really loved their King » Manila Bulletin Newsbit

Understanding Tech Debt — Beware the Buzzword

Technical debt is an overused term, often used to indicate ‘bad code’ or ‘work we don’t approve of.’ Towards and Understanding of Technical Debt by Kellan Elliot McCrea, 2016, sheds light on how technical debt looks in practice. Leaning on the concept that ‘all code is a liability’ McCrea pinpoints five distinct aspects of how ‘tech debt’ manifests itself.

1. Maintenance work.
2. Features of the codebase that resist change.
3. Operability choices that resist change.
4. Code choices that suck the will to live.
5. Dependencies that resist upgrading.

Source: Technical Debt: The Good, the Bad, and the Reckless – DZone Agile

As a contracting developer, I go for about four or five interviews a year, and I’m on the hiring side of the desk about the same number of times.

I’ve worked side-by-side with some truly great developers, and a few who were not so great.

Now, it’s not easy to predict how good a developer really is in the few short hours you have during the interview process, but I’ve got an opinion or two about what works well and what doesn’t.

And you’re about to read them.

Warning: I disagree with a lot of conventional wisdom so I’m afraid this is one of those “you’re doing it wrong” blog posts.

Source: How to hire the best developers – Hacker Noon

In my experience, there’s quite a disparity. We want people that are productive, passionate and enthusiastic. But we send out coding challenges, play 20 questions and draw a B-tree on a whiteboard.
Let’s look at some of these techniques in detail…

Source: How to hire the best developers – Hacker Noon

Having a place to go and people to see outside of school offers a reminder that they needn’t always feel that way. “What I find profoundly empowering about addressing loneliness is that the ultimate solution to loneliness lies in each of us,” Murthy says. “We can be the medicine that each other needs.”

Giving young people a room of their own, and something to do in it, is a good way to get that started.

Source: The Danish have designed a simple way to cope with loneliness — Quartz

Building a team is more complicated than collecting talent¹. I once tried to solve a problem by putting a bunch of PhDs’ in a room. While comments like that sounded good and got me a lot of projects above my level, they were rarely effective at delivering actual results.
Statements like “let’s assemble a multidisciplinary team of incredible people” are gold in meetings if you work for an organization. These statements sound intelligent. They are hard to argue with. And, most importantly, they also have no accountability built in, and they are easy to wiggle out of. If things don’t work out, who can fault a plan that meant putting smart people in a room.
Well … I can. It’s a stupid plan.
The combination of individual intelligence does not make for group intelligence. Thinking about this in the context of the Jobs quote above, “A” players provide a lot more than raw intellectual horsepower. Among other things, they also bring drive, integrity, and an ability to make others better.  “A” players want to work with other “A” players. Accepting that statement doesn’t mean they’re all “the best”.
In my experience solving difficult problems, the best talent available rarely led to the best solutions. You needed the best team. And the best team meant you had to exercise judgment and think about the problem. While there was often one individual with the idea that ultimately solved the problem, it wouldn’t have happened without the team.  The ideas others spark in us are more than we can spark in ourselves.

Source: The Importance of Working With “A” Players

I have been a pilot for 30 years, a software developer for more than 40. I have written extensively about both aviation and software engineering. Now it’s time for me to write about both together.
The Boeing 737 Max has been in the news because of two crashes, practically back to back and involving brand new airplanes. In an industry that relies more than anything on the appearance of total control, total safety, these two crashes pose as close to an existential risk as you can get. Though airliner passenger death rates have fallen over the decades, that achievement is no reason for complacency.
The 737 first appeared in 1967, when I was 3 years old. Back then it was a smallish aircraft with smallish engines and relatively simple systems. Airlines (especially Southwest) loved it because of its simplicity, reliability, and flexibility. Not to mention the fact that it could be flown by a two-person cockpit crew—as opposed to the three or four of previous airliners—which made it a significant cost saver. Over the years, market and technological forces pushed the 737 into ever-larger versions with increasing electronic and mechanical complexity. This is not, by any means, unique to the 737. Airliners constitute enormous capital investments both for the industries that make them and the customers who buy them, and they all go through a similar growth process.

Source: How the Boeing 737 Max Disaster Looks to a Software Developer – IEEE Spectrum

Not only was Darwin thinking broadly, taking in facts at all turns and on many subjects, but he was thinking carefully, This is where Munger’s admiration comes in: Darwin wanted to look at the exceptions. The exceptions to the exceptions. He was on the hunt for truth and not necessarily to confirm some highly-loved idea. Simply put, he didn’t want to be wrong about the nature of reality. To get the theory whole and correct would take lots of detail and time, as we will see.

Source: How Darwin Thought: The Golden Rule of Thinking

And here, faced with crying, I found that the data was helpful. We often say babies are “colicky,” but researchers have an actual definition of colic (three hours of crying, more than three days a week, for more than three weeks) and some estimates of what share of babies fit this description (about 2 percent). But the same data can also tell us that many babies cry just a bit less than that, and almost 20 percent of parents report their baby “cries a lot.” So I was not alone. The data also told me the crying would get better, which it eventually did.

But I also found, more so than in pregnancy, that there are limits to the utility of general information. Parenting is full of decisions, nearly all of which can be agonized over. You can and should learn about the risks and benefits of your parenting choices, but in the end you have to also think about your family preferences — about what works for you.

Source: Opinion | The Data All Guilt-Ridden Parents Need – The New York Times

How does a relational database execute SQL statements and prepared statements (Last Updated On: April 2, 2019) Follow @vlad_mihalcea
Introduction
In this article, we are going to see how a relational database executes SQL statements and prepared statements.
 
SQL statement lifecycle
The main database modules responsible for processing a SQL statement are: the Parser, the

Source: How does a relational database execute SQL statements and prepared statements – Vlad Mihalcea