Author: admin

And I think: The science fiction/horror/fantasy author David Drake very effectively and rightly, I think, puts it thus in the mouth of one of his characters, the Goddess Athene Danny Pritchard:

Force accomplishes a lot of things. They just aren’t the ones you want here. Bring in the Slammers [Regiment] and we kick ass for as long as you pay us. Six months, a year. And we kick ass even if the other side brings in mercs of their own–which they’ll do–but that’s not a problem, not if you’ve got us. So, there’s what? Three hundred thousand people….
So, you want to kill fifty kay? Fifty thousand people, let’s remember they’re people for the moment…. You see, if we go in quick and dirty, the only way that has a prayer of working is if we get them all. If we get everybody who opposes you, everybody related to them, everybody who called them master–everybody…. They’re not dangerous now, but they will be after the killing starts. Believe me. I’ve seen it often enough. Not all of them, but one in ten, one in a hundred. One in a thousand’s enough when he blasts your car down over the ocean a year from now. You’ll see. It changes people, the killing does. Once it starts, there’s no way to stop it but all the way to the end. If you figure to still live here on Tethys….
What do you think the Slammers do, milady? Work magic? We kill, and we’re good at it, bloody good. You call the Slammers in to solve your problems here and you’ll be able to cover the Port with the corpses. I guarantee it. I’ve done it, milady. In my time…

Source: Hard Power, Soft Power, Muscovy, Strategy, and My Once-Again Failure to Understand Where Niall Ferguson Is Coming From: Live from Le Pain Quotidien

Philippe: You need to take baby steps. I want to clarify one thing; these types of decisions are not solely an issue for mainframe or legacy systems. It can be a monolithic Java or .NET applications. It’s really any application which is difficult to segment. So then after their struggle on how to start, and because these applications are mission-critical, you need to enhance and you need to transform that application, but you need to be sure that this system will not collapse, or still provide services and value.
So for that you need to understand the as-is architecture, how it’s structured, to be sure that if you don’t know a specific layer or specific aspect, you will be able to investigate, define a plan, and then execute this plan. It doesn’t have to be a long approach, to rewrite from scratch into a microservice. Maybe begin by defining specific baby steps in a way to transform the presentation, as an example, and then after decouple different sections or modules.
That’s all for Part 1! Tune back in tomorrow when we’ll cover ‘as-is’ architectures.

Source: Should Every Application Leverage Microservices? Part 1 – DZone Microservices

Every economy in the world today is divided between an advanced segment, typically globally integrated, employing a minority of the labor force, and a low-productivity segment that absorbs the bulk of the workforce, often at low wages and under poor conditions. How should policymakers address this dualism?
 
CAMBRIDGE – Around the world today, the central challenge for achieving inclusive economic prosperity is the creation of sufficient numbers of “good jobs.” Without productive and dependable employment fo

Source: The Good Jobs Challenge by Dani Rodrik – Project Syndicate

“Success isn’t about how your life looks to others. It’s about how it feels to you. That’s what it means to be true to yourself.” — Michelle Obama

Asking a computer to ‘tell me about this picture’ poses other problems, though. We do not have HAL 9000, nor any path to it, and we cannot recognise any arbitrary object, but we can make a guess, of varying quality, in quite a lot of categories. So how should the user know what would work, and how does the system know what kind of guess to make? Should this all happen in one app with a general promise, or many apps with specific promises? Should you have a poster mode, a ‘solve this equation’ mode, a date mode, a books mode and a product search mode? Or should you just have mode for ‘wave the phone’s camera at things and something good will probably happen’?
This last is the approach Google is taking with ‘Lens’, which is integrated into the Android camera app next to ‘Portrait’ – point it at things and magic happens. Mostly.

Source: Cameras that understand: portrait mode and Google Lens — Benedict Evans

“Although the current entrepreneurial environment in the Philippines is not ideal, it still has great potential. In the first eight months of 2018, Southeast Asian start-ups received a record $3.16 billion in venture capital funding. The Philippines, however, is a different story. According to public data, only a small amount of money has gone to startups in the Philippines this year. Start-ups in the Philippines have received less than $50M in venture capital funding this year. For the whole of 2018, there were only seven financing cases in the Philippines, down from 10 last year and 21 in 2016,” said Mr. Xue.
The Philippines was one of the first countries in the world to launch a mobile payment service, but has made little progress in making mobile payments mainstream. For now, the Philippines remains highly dependent on cash transactions. To get Filipinos use e-payment services, they need to be given a compelling reason to feel comfortable keeping their money in e-wallets.

Source: Manzi Xue, special consultant of Huaren Capital: ‘The Philippines has demographic dividend and mobile economy potential’ | BusinessWorld

If anyone understands the immediate impacts of technical debt, it’s development teams. Engineers and engineering leaders experience firsthand the slowdowns, the death-by-a-thousand-paper-cuts, and in drastic cases, the soul-sucking repercussions of unmanaged technical debt.
But communicating those results to non-technical stakeholders is a challenge. CTOs might understand it if they were once coders themselves. Anyone without intimate or necessary knowledge of the codebase, though, is unlikely to comprehend the pain caused by technical debt. They may simply never understand (from their perspective) why engineers always make messes that need to be cleaned up later.
The key is to reframe technical debt away from the debt itself and into terms that matter to other key stakeholders. That’s how you get organization-wide buy-in for addressing technical debt, as well as the trust that your team is actively contributing to the company’s forward-looking goals.
Here are perspectives on earning that buy-in from three industry leaders: Yvette Pasqua, CTO at Meetup; Andrea Goulet, CEO at Corgibytes; and Rob Zuber, CTO at CircleCI.

Source: How to Get Buy-In for Addressing Technical Debt – DZone Agile

Across the board, all the moms mention one golden rule: Don’t shout or yell at small children.
Traditional Inuit parenting is incredibly nurturing and tender. If you took all the parenting styles around the world and ranked them by their gentleness, the Inuit approach would likely rank near the top. (They even have a special kiss for babies, where you put your nose against the cheek and sniff the skin.)

Source: How Inuit Parents Raise Kids Without Yelling — And Teach Them To Control Anger : Goats and Soda : NPR

Had Amazon really been interested in truly changing their ways, as Microsoft has proven time and again, and delivering a truly, valuable and much-needed open source community — they could have started like Microsoft and Google by open sourcing some of its own proprietary technology. Goodness knows that open source cloud has seen its share of difficulty from Solaris, to CloudStack, and even OpenStack. Why not open source parts of YOUR core business? Makes me doubt the real motivations behind your “Open Distro.” It’s really easy to offer someone else’s technology for free, I suppose.
And that’s why I understand Redis, MongoDB, and other companies like InfluxData who found themselves having to change their licenses or close source some premium features to be able to build a sustainable business, and protect themselves from such cynical and hostile corporate behavior.
Preaching open source to a vibrant open source company with deep roots in the OSS values — that has been fully transparent about their needs to monetize and maintain a stellar product, and make dubious claims about its authenticity is simply disingenuous. This is Amazon seeing someone’s shiny toy, and just wanting it for themselves.  MINE MINE MINE. This is called a fork.
And this is the dark side of open source. It is the adverse effect we would like the world of open source to be devoid of, as it will have destructive effects on everything that has been built and may be conceptualized and innovated under the auspices of open source.
 

Source: What the Fork, Amazon? – The New Stack

The best thing we can do is to provide enough information inside the message to fulfill the original use case we considered in our initial design, but also to make it usable for new microservices we haven’t thought of yet. A good starting point is to include the ID of the major Bounded Contexts entities involved or related to the fact we are communicating with this event. Of course, this will break the Law of Demeter, new microservices will need to traverse several entities, but this is a tradeoff we need to make. And that is what software architecture is all about, how to make good tradeoffs in order to have the best possible system. The ability to follow the OCP principle is something so important and useful that sometimes justifies breaking the Law of Demeter.

Source: The Open-Closed Principle at an Architectural Level – DZone Microservices