Changing these 4 beliefs will make you surprisingly happy

Sum up

Here are the 4 irrational beliefs that cause you a lot of problems:

  • “This shouldn’t be happening!”: Do you really expect to always get what you want? No. But if you really believed that you wouldn’t be shouting.
  • “I must be perfect.”: Not possible. And it’ll kill you. You can control effort, not outcome. “I will do my best” is rational. “I must be the best” is not.
  • “I should worry about this.”: Set a time to worry, to dispute, and to replace. This lets your brain know it doesn’t need to be reminding you 24/7.
  • “It’s because of my past.”: If that’s really the case, then you should be in therapy. But your problems are rarely due to dire past traumas, they’re usually due to some outdated, irrational belief you still hold. Get a friend to help you dispute and replace.

Source: Changing these 4 beliefs will make you surprisingly happy

QOTD: Concentration of power is the problem …..

Ezra Klein: 2020 Democrats Need a Power Agenda, Not Just a Policy Agenda: “Concentration of power is the problem, so redistribution of power is the policy…. The Roosevelt Institute’s manifesto-ish new paper, ‘New Rules For The 21st Century: Corporate Power, Public Power, and the Future of the American Economy’…. Concentration of power is the problem, so redistribution of power is the policy…. TThe traditional economic analysis is that growth comes from innovation, innovation comes from competitive markets, and competitive markets come from government getting the hell out of the way. The Roosevelt authors say we’ve gotten that dead wrong. Yes, growth comes from innovation, and innovation comes from competitive markets, but competitive markets—be they economic or political—don’t come from a laissez-faire government. They come from policymakers breaking up concentrations of power, because the last thing power wants is competition…

File Handling Issues in SQL Server

For access denied issues when reading files in SQL Server, the service of SQL Server needs to have rights to the folder.
The user that should be searched:
NT SERVICE\MSSQLSERVER
Source:
https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-file-system-permissions-for-database-engine-access?view=sql-server-2017

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

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

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

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

How to hire the best developers – Hacker Noon

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

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

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

The Importance of Working With “A” Players

Building a team is more complicated than collecting talent1. 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