Ship Carrying EVs Abandoned in Pacific After Catching Fire
A ship carrying about 3,000 cars to Mexico was abandoned in the middle of the Pacific Ocean after catching fire Tuesday.
Smoke was first seen coming from a deck on the Morning Midas that was carrying electric vehicles, the ship's manager Zodiac Maritime said in a statement. It has about 800 EVs on board.
Hashtags
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
Forbes
21 minutes ago
- Forbes
Platform Engineering At A Crossroads: Golden Paths Or Dark Alleyways
Following the golden path to platform engineering success is not without its pitfalls and pernicios ... More passageways. getty Automation equals efficiency. It's a central promise that's now permeating every segment of the software application development lifecycle. From robotic process automation accelerators that work at the user level, through encapsulated best practices applied throughout the networking connection tier used to bring applications to production… and onward (especially now) to the agentic software functions that can take natural language prompts (written by developers) and convert them to software test cases and, subsequently, also write the code for those tests. Automation represents a key efficiency play that all teams are now being compelled to adopt. As an overarching practice now carrying automated software development tooling forward, platform engineering is widely regarded as (if not quite a panacea) an intelligent approach to encoding infrastructure services and development tools in a way that means developers can perform more self-service functions without having to ask the operations team for backup. Platform engineering encapsulates the deliberate design and delivery of internal software application development tools, services and processes that define how software engineers build software. It's a holistic approach that covers the underlying processes, people and (perhaps more crucially of all), the cultural workflow mindset of an organization. At the keyboard, platform engineering is not necessarily all about implementing new technologies (although the omniscient specter of agentic AI will never be far away); it's about fostering consistency and a shared understanding across diverse teams. Devotees who preach the gospel according to platform engineering talk of its ability to lead towards so-called "golden paths" today. These can be described as standardarized workflow routes where infrastructure and configuration parameters for software development are encoded, ratified and documented. Often referred to as an 'opinionated' software practice (i.e. one that takes a defined path and does things one way, not the other way) that help individual software engineers stay close to tooling and processes that will be used by all other developers in a team or department. 'One way to think of a golden path is to imagine baking a cake. The steps required to bake a cake include pre-heating the oven to a specific temperature, gathering the right baking tools… and having the necessary ingredients. It's more than following a recipe, it's also making sure you use the right tools and techniques. If you want more people to bake the same cake, you find ways to become more consistent and efficient, explains Red Hat , on its DevOps pages. According to Derek Webber, VP of engineering at AI-enabled software quality engineering company Tricentis , platform engineering does have the potential to be golden, but it can also lead teams down a dark and dusty track into the Wild West. Why The Wild West? 'Yes, the promise of platform engineering lies in creating golden paths for software delivery. However, the absence of a traditional structured approach to software development often leads to what can only be described as the 'Wild West' of software development, particularly within large, scaling enterprises,' stated Webber. 'In such environments, each product team might independently craft their own unique pipelines, tools and processes. While this might afford initial autonomy, it inevitably leads to fragmentation. As organizations grow from a few dozen to hundreds or thousands of engineers, the tight-knit integration and level of shared understanding that characterizes a startup are lost. Developers become isolated, building 'unique snowflakes' of software pipelines that are difficult to maintain, understand and transfer knowledge across.' This fragmentation might be argued to severely hamper an organization's ability to be flexible and nimble, with an ability to move fast (remember the pandemic, yeah, that kind of change). Why would this be so? Because every new feature, every bug fix and even basic team reorganization becomes a slower and more laborious task. This can happen because of cross-team dependencies when everything is so formally encoded, it can happen because developers see their work as a project, rather than it being a product… and it can happen simply as a result of poorly documented tools in the platform engineering firmament. A fragmented coding landscape also obviously presents challenges to an organization's security posture, making it more difficult to ensure consistent compliance and vulnerability management across all services. DevEx, The Software World On Time 'The true power of platform engineering, especially when championed by a dedicated developer experience (DevEx) team, comes when it is able to balance two critical, often conflicting, objectives: speed and quality. This can be achieved by providing the necessary checks and balances that promote operational consistency and efficiency at scale,' said Webber. 'A core tenet of effective platform engineering is, therefore, the integration of testing from the outset to ensure quality is inherent, not an afterthought. While the industry has long advocated a 'shift left' approach, empowering developers to take on more testing responsibilities earlier in the development lifecycle, it's vital not to overcorrect.' Shifting everything left without considering the end-to-end product can lead to a different kind of fragmentation further down the line. The suggestion here is that platform engineering, via, through and under the auspices of a DevEx team, enables a more holistic approach. Webber says he's convinced that the DevEx team plays a pivotal role in creating a consistent testing framework when applied in the realm of platform engineering. It works by providing developers with readily available, uniform tools and processes. It bridges the gap in domain knowledge that often plagues large organizations, ensuring software engineers have the context needed to build robust solutions that actually work and actually scale. By providing pipeline automation, self-serve tools, environment management and established practices for observability and compliance, the DevEx team frees developers from the burden of figuring out how to build the pipeline and hook in tools. They can instead focus on what they build: the core product functionality. 'This shift in responsibility is transformative,' enthused Tricentis' Webber. 'When developers aren't forced to create their own 'special flavour' of every operational component, they gain immense speed and agility. They can move faster, knowing that the underlying platform provides reliable, secure and quality-assured foundations.' It appears that the consistency instilled by platform engineering, not just in tools, but in processes and mindset, becomes the bedrock of what this approach means. Webber and others agree that this could be particularly critical in an era where advancements like AI (and the future allure of can rapidly generate code, necessitating robust and consistent guardrails to maintain quality and security. CNCF Overview View 'We're seeing real traction in the CNCF ecosystem where platform engineering, when paired with strong developer experience practices, helps teams improve efficiency and avoid fragmented tooling. The goal isn't rigid standardization; it's creating shared, supported paths that scale with the organization. Especially as AI speeds up engineering development, having consistent, observable and secure platforms in a cloud-native fashion is what keeps innovation sustainable,' said Chris Aniszczyk , CTO, Cloud Native Computing Foundation, a global non-profit dedicated to promoting open computing standards and platforms. Will Fleury, VP of engineering at enterprise AI coding agent company Zencoder sees platform engineering as an opportunity and a challenge. "One squad [developer team], one technology stack each? That's a tax on every software development sprint," he observes. 'The real price of skipping platform engineering isn't the complexity it might add, it's the chaos that fills the gap if we do it wrong. Building and running an internal developer platform takes effort, but letting every squad roll its own infrastructure, compliance hooks and operational plumbing burns far more time, money and ultimately complexity.' Golden Path, Tunnel Vision? It's important to remember that the focus on internal workflows can miss a critical dimension. Platform discussions obsess over shift left (test early) but equally important is what Soham Ganatra , co-founder at Composio calls 'shift out' i.e. when a new service has to handshake with a payments rail or partner API. "If your platform can't make that external connection trivial, developers will tunnel under a paved road and the whole notion of a golden path collapses,' said Ganatra. He saus he has seen teams spend months perfecting internal developer workflows only to watch everything fall apart at the network boundary. 'A beautiful continuous integration and continuous delivery pipeline means nothing if deploying to production requires three Slack messages, two Jira tickets and a phone call to someone in a different timezone just to get firewall rules updated. The platform needs to extend beyond an organization's own chart; it has to anticipate and smooth over the messy realities of partner integrations, compliance audits and the fact that your biggest customer is still running Internet Explorer 11 in production," he said. Shared, standardized, supported software What this whole discussion aims to champion is not DevEx instead of platform engineering, but platform engineering with a crucial developer experience element in it to help avoid the use of isolated or custom-built tools in a shared, standardized and centrally supported ecosystem. For developers following the yellow brick road towards what they hope is elevation to a platform engineering golden path, we need to engineer people, processes and product just as much as we do platform. As the use of AI coding tools deepens across the software industry, it's actually the cultural human workplace factors that will now have an amplified effect on whether software projects succeed or fail.
Associated Press
21 minutes ago
- Associated Press
Trump's tax and spending cuts bill clears key Senate vote as Republicans race to pass it by July 4
The Associated Press is an independent global news organization dedicated to factual reporting. Founded in 1846, AP today remains the most trusted source of fast, accurate, unbiased news in all formats and the essential provider of the technology and services vital to the news business. More than half the world's population sees AP journalism every day.
Associated Press
21 minutes ago
- Associated Press
A tour guide of Ultra Orthodox Jewish culture in NYC dishes up a side of insider knowledge
The Associated Press is an independent global news organization dedicated to factual reporting. Founded in 1846, AP today remains the most trusted source of fast, accurate, unbiased news in all formats and the essential provider of the technology and services vital to the news business. More than half the world's population sees AP journalism every day.
