January 02, 2023
Kannan Subbiah
FCA | CISA | CGEIT | CCISO | GRC Consulting | Independent Director | Enterprise & Solution Architecture | Former Sr. VP & CTO of MF Utilities | BU Soft Tech | itTrident
Promise #1: The cloud will save money. Disappointment: It never did, and still won’t Why it won’t: You can buy servers as cheaply as the cloud providers, and they need to add a profit margin when they charge you for using them. What you should promise instead: Unlike on-premises infrastructure, the cloud lets IT easily add capacity in small increments when demand requires it. And — and this is the biggie — it also lets IT shed capacity when it’s no longer needed. The result? When demand is seasonal or unpredictable the cloud truly does save money. But when demand is steady, or increases in demand are predictable, on-premises infrastructure costs less. In the cloud, fixed costs are small but incremental costs are big. The costs of on-premises systems are the opposite. ...?Promise #4: ‘Agile’ means no more big-project failures.?Disappointment: Your name will be on some miserable Agile project failures this year?What’s going to go wrong: Your company is going to make three Agile mistakes. The first, and worst, is that it won’t lose the habit of insisting on multitasking — developers will still be asked to juggle multiple competing projects, and their top priority will still be the next phone call.
Cybersecurity training keeps employees, customers, and vendors safe from cyberattacks. Take the initiative to seek out top-of-the-line training resources that will walk you through every aspect of promoting a secure environment. Training does not need to be expensive. Learn how to avoid data breaches, cultivate a security-first mindset, and maintain airtight security. While no measure can prevent a cyberattack entirely, proper training can help minimize your risk and reduce the chance of a breach. In addition, continue to sweat the small stuff. While one weak password or phishing email may not seem like a big deal, it’s in your best interest to take every threat seriously. Implement strong password complexity controls and policies, develop and maintain phishing campaigns, track user activity, and create policies for sharing information on the internet. For example, posting information on social media could reveal answers to common security questions. Staying vigilant will help your organization avoid trouble in the future.
We are yet to witness the full potential of IoT, but before that, we need to overcome a big challenge. The sensors that make IoT networks possible require power to stay functional, and unfortunately, our existing energy solutions are not enough to support this demand. A team of researchers at King Abdullah University of Science and Technology (KAUST) in Saudi Arabia has been working on this problem and in their latest study, they propose an interesting solution. The authors reveal details about wireless-powered electronics that promise to meet the energy demands of IoT networks in a sustainable and eco-friendly manner. Sensors are currently powered by technologies like Li-ion batteries. Although batteries can power a large network of devices, they need to be replaced again and again. Therefore a battery-based approach is expensive, unsustainable, and harmful to the environment. For instance, conventional batteries are made of metals that are procured through mining activities resulting in air and soil contamination. Plus, when these batteries are not carefully disposed of, they release toxic chemicals into our environment.
领英推荐
Waterfall and agile culture are different forms of managing software projects, but they are made of the same constituent concept: people managing people. The values we covered, on the other hand, are not interchangeable. They are different in kind, they are indeed the quintessential difference between agile and waterfall. Following the scrum guide by the book, having squads, agile coaches, dailies, and meetups might make you show up as agile, but unless your values are aligned with the Manifesto, you’re just dressing waterfall as agility. This is precisely the scenario we have been witnessing in the last few years. As more and more companies see the results of strong agile culture creating unicorns and industry juggernauts, more of them want a quick way to execute digital transformation. What happens is that they start practicing agile, but keep the waterfall values of control with a lack of flexibility and hierarchy. Even worse, since the number of successfully transformed companies is way smaller than those who just pretend to have transitioned, more and more people have no experience with agile values, leading them to believe that doing agile with waterfall values is perfectly normal.
“Rust to WebAssembly is one of the most mature paths because there’s a lot of overlap between the communities,” Gardner told The New Stack. “A lot of people are interested in both Rust and WebAssembly at the same time.” It’s not an either “Rust or JavaScript” or even “WebAssembly or JavaScript” situation, he said. It’s possible to blend WebAssembly with JavaScript. “You’re going to see some people rewrite for WebAssembly, but you’re going to see some people take advantage of WebAssembly where appropriate, and then use JavaScript for connecting the various pieces under the hood, and maybe running portions of the application as necessary,” he said. ...?Chris Siebenmann, a Unix systems administrator at the University of Toronto’s CS Labs, has a theory about that: Languages spread when developers like using the language to accomplish things that matter to them. Right now, that language is Rust. “Rust is a wave of the future because a lot of people are fond of it and they are writing more and more things in Rust, and some of these things are things that matter to plenty of people,” Siebenmann wrote in 2021.
According to Martin Fowler, DTO is: “An object that carries data between processes in order to reduce the number of method calls. When you're working with a remote interface, such as Remote Facade, each call to it is expensive. As a result, you need to reduce the number of calls. The solution is to create a Data Transfer Object that can hold all the data for the call.” So, initially, DTOs were intended to be used as a container for remote calls. In a perfect world, DTOs should not have any logic inside and be immutable. We use them only as state holders. Nowadays, many developers create DTOs to transfer data between application layers, even for in-app method calls. If we use JPA as a persistence layer, we can read an opinion that it is a bad practice to use entities in the business logic, and all entities should be immediately replaced by DTOs. We recently introduced DTO support in the JPA Buddy plugin. The plugin can create DTOs based on JPA entities produced by data access layer classes and vice versa – create entities based on POJOs. This allowed us to look at DTOs closer and see how we can use them on different occasions.