Developer
Auto Added by WPeMatico
Auto Added by WPeMatico
No company is completely insulated from the macroeconomic fallout of COVID-19, but we are seeing some companies fare better than others, especially those providing ways to collaborate online. Count Atlassian in that camp, as it provides a suite of tools focused on working smarter in a digital context.
At a time when many employees are working from home, Atlassian’s product approach sounds like a recipe for a smash hit. But in its latest earnings report, the company detailed slowing growth, not the acceleration we might expect. Looking ahead, it’s predicting more of the same — at least for the short term.
Part of the reason for that — beyond some small-business customers, hit by hard times, moving to its new free tier introduced last March — is the pain associated with moving customers off of older license revenue to more predictable subscription revenue. The company has shown that it is willing to sacrifice short-term growth to accelerate that transition.
We sat down with Atlassian CRO Cameron Deatsch to talk about some of the challenges his company is facing as it navigates through these crazy times. Deatsch pointed out that in spite of the turbulence, and the push to subscriptions, Atlassian is well-positioned with plenty of cash on hand and the ability to make strategic acquisitions when needed, while continuing to expand the recurring-revenue slice of its revenue pie.
Deatsch told us that Atlassian could not fully escape the pandemic’s impact on business, especially in April and May when many companies felt it. His company saw the biggest impact from smaller businesses, which cut back, moved to a free tier, or in some cases closed their doors. There was no getting away from the market chop that SMBs took during the early stages of COVID, and he said it had an impact on Atlassian’s new customer numbers.
Image Credits: Atlassian
Still, the company believes it will recover from the slow down in new customers, especially as it begins to convert a percentage of its new, free-tier users to paid users down the road. For this quarter it only translated into around 3000 new customers, but Deatsch didn’t seem concerned. “The customer numbers were off, but the overall financials were pretty strong coming out of [fiscal] Q4 if you looked at it. But also the number of people who are trying our products now because of the free tier is way up. We saw a step change when we launched free,” he said.
Powered by WPeMatico
Suse today announced that it has contributed EiriniX, a framework for building extensions for Eirini, a technology that brings support for Kubernetes-based container orchestration to the Cloud Foundry platform-as-a-service project.
About a year ago, Suse also contributed the KubeCF project to the foundation, which itself allows the Cloud Foundry Application Runtime — the core of Cloud Foundry — to run on top of Kubernetes.
“At Suse we are developing upstream first as much as possible,” said Thomas Di Giacomo, president of Engineering and Innovation at Suse. “So, after experiencing the value of contributing KubeCF to the Foundation earlier this year, we decided it would be beneficial to both the Cloud Foundry community and the EiriniX team to do it again. We have seen an uptick in contributions to and usage of KubeCF since it became a Foundation project, indicating that more organizations are investing developer time into the upstream. Contributing EiriniX to the Foundation is a surefire way to get the broader community involved.”
Suse first demonstrated EiriniX a year ago. The tool implements features like the ability to SSH into a container and debug it, for example, or to use alternative logging solutions for KubeCF.
“There is significant value in contributing this project to the Foundation, as it ensures that other project teams looking for a similar solution to creating Extensions around Eirini will not reinvent the wheel,” said Chip Childers, executive director, Cloud Foundry Foundation. “Now that EiriniX exists within the Foundation, developers can take full advantage of its library of add-ons to Eirini and modify core features of Cloud Foundry. I’m excited to see all of the use cases for this project that have not yet been invented.”
Powered by WPeMatico
Across the board, industries need to embrace modern workflows to keep up with the speed of startups. And out of all the various methodologies, I find the “lean methodology” to be the most intriguing of them all. It’s a unique combination of pragmatism and a higher purpose.
Lean methodology descends directly from the Toyota Production Systems (TPS), which is based on a philosophy of eliminating waste to achieve efficiency in processes. It relies heavily on the mindset of “just-in-time,” making only “what is needed when needed, and in the amount needed.” In software development, this means only developing the features your clients need, and only when they need them.
To emphasize the point and stir some creative juices, let’s look at the Japanese concepts of muda, mura and muri, and how this applies to being lean when we are building and shipping software.
Muda is the “waste” we are working to remove that is directly hurting efficiency. Waste is any activity that doesn’t create value, in the form of the products and services we offer. As every engineer knows, spending half the day in meetings is a painful waste of time.
Mura is “unevenness,” referring to any variance in the process itself or the output generated. In software development, “mura” causes unpredictability that makes it impossible to embrace a “just-in-time” mindset. If the quality of a new upcoming feature is uncertain, then additional time and resources will have to be reserved for quality assurance and bug-fixing efforts. It’s better to know upfront what you are going to get, how long it will take and what the cost will be.
Muri is “overburden,” which happens when we demand the unreasonable from our team, tools and processes. If we want to deliver a specific feature just-in-time, then we must allocate the appropriate time and resources. Giving our engineering teams too many simultaneous tasks, or failing to give them the tools necessary to succeed, will only lead to disappointment in time, quantity, quality or cost.
Diving deeper into muda — what I consider the cardinal sin of lean methodology — here are the forms of waste we should always be on the lookout for:
Powered by WPeMatico
Mirantis, the company that recently bought Docker’s enterprise business, today announced that it has acquired Lens, a desktop application that the team describes as a Kubernetes-integrated development environment. Mirantis previously acquired the team behind the Finnish startup Kontena, the company that originally developed Lens.
Lens itself was most recently owned by Lakend Labs, though, which describes itself as “a collective of cloud native compute geeks and technologists” that is “committed to preserving and making available the open-source software and products of Kontena.” Lakend open-sourced Lens a few months ago.
“The mission of Mirantis is very simple: We want to be — for the enterprise — the fastest way to [build] modern apps at scale,” Mirantis CEO Adrian Ionel told me. “We believe that enterprises are constantly undergoing this cycle of modernizing the way they build applications from one wave to the next — and we want to provide products to the enterprise that help them make that happen.”
Right now, that means a focus on helping enterprises build cloud-native applications at scale and, almost by default, that means providing these companies with all kinds of container infrastructure services.
“But there is another piece of the story that’s always been going through our minds, which is, how do we become more developer-centric and developer-focused, because, as we’ve all seen in the past 10 years, developers have become more and more in charge off what services and infrastructure they’re actually using,” Ionel explained. And that’s where the Kontena and Lens acquisitions fit in. Managing Kubernetes clusters, after all, isn’t trivial — yet now developers are often tasked with managing and monitoring how their applications interact with their company’s infrastructure.
“Lens makes it dramatically easier for developers to work with Kubernetes, to build and deploy their applications on Kubernetes, and it’s just a huge obstacle-remover for people who are turned off by the complexity of Kubernetes to get more value,” he added.
“I’m very excited to see that we found a common vision with Adrian for how to incorporate Lens and how to make life for developers more enjoyable in this cloud-native technology landscape,” Miska Kaipiainen, the former CEO of Kontena and now Mirantis’ director of Engineering, told me.
He describes Lens as an IDE for Kubernetes. While you could obviously replicate Lens’ functionality with existing tools, Kaipiainen argues that it would take 20 different tools to do this. “One of them could be for monitoring, another could be for logs. A third one is for command-line configuration, and so forth and so forth,” he said. “What we have been trying to do with Lens is that we are bringing all these technologies [together] and provide one single, unified, easy to use interface for developers, so they can keep working on their workloads and on their clusters, without ever losing focus and the context of what they are working on.”
Among other things, Lens includes a context-aware terminal, multi-cluster management capabilities that work across clouds and support for the open-source Prometheus monitoring service.
For Mirantis, Lens is a very strategic investment and the company will continue to develop the service. Indeed, Ionel said the Lens team now basically has unlimited resources.
Looking ahead, Kaipiainen said the team is looking at adding extensions to Lens through an API within the next couple of months. “Through this extension API, we are actually able to collaborate and work more closely with other technology vendors within the cloud technology landscape so they can start plugging directly into the Lens UI and visualize the data coming from their components, so that will make it very powerful.”
Ionel also added that the company is working on adding more features for larger software teams to Lens, which is currently a single-user product. A lot of users are already using Lens in the context of very large development teams, after all.
While the core Lens tools will remain free and open source, Mirantis will likely charge for some new features that require a centralized service for managing them. What exactly that will look like remains to be seen, though.
If you want to give Lens a try, you can download the Windows, macOS and Linux binaries here.
Powered by WPeMatico
A lot of “partnerships” between tech companies don’t get very far beyond a press release and maybe some half-hearted co-selling attempts. When Atlassian sold its chat services to Slack in 2018, the two companies said they would form a new partnership and with Atlassian leaving the chat space, a lot of people were skeptical about what that would really mean.
Since then, things got pretty quiet around the collaboration between the two companies, but today the companies announced some of the deep integration work they’ve done, especially within Slack .
Over the course of the last two years, Slack and Atlassian shipped 11 product integrations, which now see about a million active users every month, with Jira being the most often used integration, followed by Halp, which Atlassian acquired earlier this year.
Every month, Atlassian currently sends 42 million Jira notifications to Slack — and that number continues to grow.
At the core of these integrations is the ability to get rich unfurls of deep links to Atlassian products in Slack, no matter whether that’s in DMs, public or private channels. Coming soon, those unfurls will become a default feature within Slack, even if the user who is seeing the link isn’t an Atlassian user yet.
“Today, if you do drop a Jira link in your channel and you’re not a user — or even if you are and you’re not authed in — you just see a link,” Brad Armstrong said.
“You don’t get the benefit of the unfurl. And so one of the things we’re doing is making that unfurl available to everybody, regardless of whether you are logged in and regardless of whether you’re even an Atlassian customer.”
The two companies also worked closely together on making moving between the products easier. If you are a Jira user, for example, you’ll soon be able to click on a link in Slack and if you’re not currently logged into your Atlassian account, you’ll be automatically logged in. The two companies are taking this even further by automatically creating Jira accounts for users when they come from Slack.
“Even if you’re not a user, when you click on the link, we will then map you from Slack and create a Jira user for you that provisions you and auths you in so you’re immediately becoming a Jira user by virtue of wanting to collaborate on that piece of content in Slack,” Armstrong explained.
That, the two companies argue, turns Slack into something akin to a passport that gives you access to the Atlassian product suite — and that should also make onboarding a lot easier for new users.
“As you could probably imagine, as you know, onboarding is a pain, it’s hard because you have different roles, different size teams, so on and so forth,” said Bryant Lee, Atlassian’s head of product partnerships. “And that’s where you see some of the authentication stuff, the unfurling discovery piece really being an understanding of what those practices are. But the way that we look at it is not just about the product but people, products and practices. So it’s really about understanding who it is that we’re trying to optimize for.”
In addition to these new integrations that are launching soon, the two companies are also expanding their co-marketing efforts, starting with a new 50%-off offer for Atlassian users who want to also use Slack.
“We’re building on the strong foundation of our partnership’s success from the past two years, which has yielded tremendous shared customer momentum and impactful product integrations,” said Slack co-founder and CEO Stewart Butterfield . “Thanks to our strategic alliance, Slack and Atlassian have become the technology stack of choice for developer teams.”
Powered by WPeMatico
It’s 2020 and the world has changed remarkably, including in how companies screen data science candidates. While many things have changed, there is one change that stands out above the rest. At The Data Incubator, we run a data science fellowship and are responsible for hundreds of data science hires each year. We have observed these hires go from a rare practice to being standard for over 80% of hiring companies. Many of the holdouts tend to be the largest (and traditionally most cautious) enterprises. At this point, they are at a serious competitive disadvantage in hiring.
Historically, data science hiring practices evolved from software engineering. A hallmark of software engineering interviewing is the dreaded brain teaser, puzzles like “How many golf balls would fit inside a Boeing 747?” or “Implement the quick-sort algorithm on the whiteboard.” Candidates will study for weeks or months for these and the hiring website Glassdoor has an entire section devoted to them. In data science, the traditional coding brain teaser has been supplemented with statistics ones as well — “What is the probability that the sum of two dice rolls is divisible by three?” Over the years, companies are starting to realize that these brain teasers are not terribly effective and have started cutting down their usage.
In their place, firms are focusing on project-based data assessments. These ask data science candidates to analyze real-world data provided by the company. Rather than having a single correct answer, project-based assessments are often more open-ended, encouraging exploration. Interviewees typically submit code and a write-up of their results. These have a number of advantages, both in terms of form and substance.
First, the environment for data assessments is far more realistic. Brain teasers unnecessarily put candidates on the spot or compel them to awkwardly code on a whiteboard. Because answers to brain teasers are readily Google-able, internet resources are off-limits. On the job, it is unlikely that you’ll be asked to code on a whiteboard or perform mental math with someone peering over your shoulder. It is incomprehensible that you’ll be denied internet access during work hours. Data assessments also allow the applicants to complete the assessment at a more realistic pace, using their favorite IDE or coding environment.
“Take-home challenges give you a chance to simulate how the candidate will perform on the job more realistically than with puzzle interview questions,” said Sean Gerrish, an engineering manager and author of “How Smart Machines Think.”
Second, the substance of data assessments is also more realistic. By design, brainteasers are tricky or test knowledge of well-known algorithms. In real life, one would never write these algorithms by hand (you would use one of the dozens of solutions freely available on the internet) and the problems encountered on the job are rarely tricky in the same way. By giving candidates real data they might work with and structuring the deliverable in line with how results are actually shared at the company, data projects are more closely aligned with actual job skills.
Jesse Anderson, an industry veteran and author of “Data Teams,” is a big fan of data assessments: “It’s a mutually beneficial setup. Interviewees are given a fighting chance that mimics the real-world. Managers get closer to an on-the-job look at a candidate’s work and abilities.” Project-based assessments have the added benefit of assessing written communication strength, an increasingly important skill in the work-from-home world of COVID-19.
Finally, written technical project work can help avoid bias by de-emphasizing traditional but prejudicially fraught aspects of the hiring process. Resumes with Hispanic and African American names receive fewer callbacks than the same resume with white names. In response, minority candidates deliberately “whiten” their resumes to compensate. In-person interviews often rely on similarly problematic gut feel. By emphasizing an assessment closely tied to job performance, interviewers can focus their energies on actual qualifications, rather than relying on potentially biased “instincts.” Companies looking to embrace #BLM and #MeToo beyond hashtagging may consider how tweaking their hiring processes can lead to greater equality.
The exact form of data assessments vary. At The Data Incubator, we found that over 60% of firms provide take-home data assessments. These best simulate the actual work environment, allowing the candidate to work from home (typically) over the course of a few days. Another roughly 20% require interview data projects, where candidates analyze data as a part of the interview process. While candidates face more time pressure from these, they also do not feel the pressure to ceaselessly work on the assessment. “Take-home challenges take a lot of time,” explains Field Cady, an experienced data scientist and author of “The Data Science Handbook.” “This is a big chore for candidates and can be unfair (for example) to people with family commitments who can’t afford to spend many evening hours on the challenge.”
To reduce the number of custom data projects, smart candidates are preemptively building their own portfolio projects to showcase their skills and companies are increasingly accepting these in lieu of custom work.
Companies relying on old-fashioned brainteasers are a vanishing breed. Of the recalcitrant 20% of employers still sticking with brainteasers, most are the larger, more established enterprises that are usually slower to adapt to change. They need to realize that the antiquated hiring process doesn’t just look quaint, it’s actively driving candidates away. At a recent virtual conference, one of my fellow panelists was a data science new hire who explained that he had turned down opportunities based on the firm’s poor screening process.
How strong can the team be if the hiring process is so outmoded? This sentiment is also widely shared by the Ph.D.s completing The Data Incubator’s data science fellowship. Companies that fail to embrace the new reality are losing the battle for top talent.
Powered by WPeMatico
Quantum computers exploit the seemingly bizarre yet proven nature of the universe that until a particle interacts with another, its position, speed, color, spin and other quantum properties coexist simultaneously as a probability distribution over all possibilities in a state known as superposition. Quantum computers use isolated particles as their most basic building blocks, relying on any one of these quantum properties to represent the state of a quantum bit (or “qubit”). So while classical computer bits always exist in a mutually exclusive state of either 0 (low energy) or 1 (high energy), qubits in superposition coexist simultaneously in both states as 0 and 1.
Things get interesting at a larger scale, as QC systems are capable of isolating a group of entangled particles, which all share a single state of superposition. While a single qubit coexists in two states, a set of eight entangled qubits (or “8Q”), for example, simultaneously occupies all 2^8 (or 256) possible states, effectively processing all these states in parallel. It would take 57Q (representing 2^57 parallel states) for a QC to outperform even the world’s strongest classical supercomputer. A 64Q computer would surpass it by 100x (clearly achieving quantum advantage) and a 128Q computer would surpass it a quintillion times.
In the race to develop these computers, nature has inserted two major speed bumps. First, isolated quantum particles are highly unstable, and so quantum circuits must execute within extremely short periods of coherence. Second, measuring the output energy level of subatomic qubits requires extreme levels of accuracy that tiny deviations commonly thwart. Informed by university research, leading QC companies like IBM, Google, Honeywell and Rigetti develop quantum engineering and error-correction methods to overcome these challenges as they scale the number of qubits they can process.
Following the challenge to create working hardware, software must be developed to harvest the benefits of parallelism even though we cannot see what is happening inside a quantum circuit without losing superposition. When we measure the output value of a quantum circuit’s entangled qubits, the superposition collapses into just one of the many possible outcomes. Sometimes, though, the output yields clues that qubits weirdly interfered with themselves (that is, with their probabilistic counterparts) inside the circuit.
QC scientists at UC Berkeley, University of Toronto, University of Waterloo, UT Sydney and elsewhere are now developing a fundamentally new class of algorithms that detect the absence or presence of interference patterns in QC output to cleverly glean information about what happened inside.
A fully functional QC must, therefore, incorporate several layers of a novel technology stack, incorporating both hardware and software components. At the top of the stack sits the application software for solving problems in chemistry, logistics, etc. The application typically makes API calls to a software layer beneath it (loosely referred to as a “compiler”) that translates function calls into circuits to implement them. Beneath the compiler sits a classical computer that feeds circuit changes and inputs to the Quantum Processing Unit (QPU) beneath it. The QPU typically has an error-correction layer, an analog processing unit to transmit analog inputs to the quantum circuit and measure its analog outputs, and the quantum processor itself, which houses the isolated, entangled particles.
Powered by WPeMatico
Merico, a startup that gives companies deeper insights into their developers’ productivity and code quality, today announced that it has raised a $4.1 million seed round led by GGV Capital, with participation from Legend Star and previous investor Polychain Capital. The company was originally funded by the open source-centric firm OSS Capital.
Merico head of business development Maxim Wheatley tells me that the company plans to use the new funding to enhance and expand its existing technology and marketing efforts. As a remote-first startup, Merico already has team members in the U.S., Brazil, France, Canada, India and China.
“In keeping with our roots and mission in open source, we will be focusing some of these new resources to engage more collaboratively with open-source foundations, contributors and maintainers,” he added.
The idea behind Merico was born out of two key observations, Wheatley said. First of all, the team wanted to create a better way to analyze developer productivity and the quality of the code they generate. Some companies still simply use the number of lines of code generated by a developer to allocate bonuses for their teams, for example, which isn’t a great metric by any means. In addition, the team also wanted to find ways to better allocate income and recognition to the community members of open-source projects based on the quality of their contributions.
The company’s tool is systems agnostic because it bases its analysis on the codebase and workflow tools instead of looking at lines of codes or commit counts, for example.
“Merico evaluates the actual code, in addition to related processes, and places productivity in the context of quality and impact,” said Merico CTO Hezheng Yin . “In this process, we evaluate impact leveraging dependency relationships and examine fundamental indicators of quality including bug density, redundancy, modularity, test-coverage, documentation-coverage, code-smell and more. By compiling these signals into a single point of truth, Merico can determine the quality and the productivity of a developer or a team in a manner that more accurately reflects the nature of the work.”
As of now, Merico supports code written in Java, JavaScript (Vue.js and React.js), TypeScript, Go, C, C++, Ruby and Python, with support for other languages coming later.
“Merico’s technology delivers the most advanced code analytics that we’ve seen on the market,” said GGV’s Jenny Lee . “With the Merico team, we saw an opportunity to empower the organizations of tomorrow with insight. In this era of remote transformation, there’s never been a more critical time to bring this visibility to the enterprise and to open source; we can’t wait to see how this technology drives innovation in both technology and management.”
Powered by WPeMatico
Every major technology breakthrough of our era has gone through a similar cycle in pursuit of turning fiction to reality.
It starts in the stages of scientific discovery, a pursuit of principle against a theory, a recursive process of hypothesis-experiment. Success of the proof of principle stage graduates to becoming a tractable engineering problem, where the path to getting to a systemized, reproducible, predictable system is generally known and de-risked. Lastly, once successfully engineered to the performance requirements, focus shifts to repeatable manufacturing and scale, simplifying designs for production.
Since theorized by Richard Feynman and Yuri Manin, quantum computing has been thought to be in a perpetual state of scientific discovery. Occasionally reaching proof of principle on a particular architecture or approach, but never able to overcome the engineering challenges to move forward.
That’s until now. In the last 12 months, we have seen several meaningful breakthroughs from academia, venture-backed companies, and industry that looks to have broken through the remaining challenges along the scientific discovery curve. Moving quantum computing from science fiction that has always been “five to seven years away,” to a tractable engineering problem, ready to solve meaningful problems in the real world.
Companies such as Atom Computing* leveraging neutral atoms for wireless qubit control, Honeywell’s trapped ions approach, and Google’s superconducting metals, have demonstrated first-ever results, setting the stage for the first commercial generation of working quantum computers.
While early and noisy, these systems, even at just 40-80 error-corrected qubit range, may be able to deliver capabilities that surpass those of classical computers. Accelerating our ability to perform better in areas such as thermodynamic predictions, chemical reactions, resource optimizations and financial predictions.
As a number of key technology and ecosystem breakthroughs begin to converge, the next 12-18 months will be nothing short of a watershed moment for quantum computing.
Here are eight emerging trends and predictions that will accelerate quantum computing readiness for the commercial market in 2021 and beyond:
1. Dark horses of QC emerge: 2020 will be the year of dark horses in the QC race. These new entrants will demonstrate dominant architectures with 100-200 individually controlled and maintained qubits, at 99.9% fidelities, with millisecond to seconds coherence times that represent 2x -3x improved qubit power, fidelity and coherence times. These dark horses, many venture-backed, will finally prove that resources and capital are not sole catalysts for a technological breakthrough in quantum computing.
Powered by WPeMatico
Microsoft today announced the launch of a new open-source service mesh based on the Envoy proxy. The Open Service Mesh is meant to be a reference implementation of the Service Mesh Interface (SMI) spec, a standard interface for service meshes on Kubernetes that has the backing of most of the players in this ecosystem.
The company plans to donate Open Service Mesh to the Cloud Native Computing Foundation (CNCF) to ensure that it is community-led and has open governance.
“SMI is really resonating with folks and so we really thought that there was room in the ecosystem for a reference implementation of SMI where the mesh technology was first and foremost implementing those SMI APIs and making it the best possible SMI experience for customers,” Microsoft director of partner management for Azure Compute (and CNCF board member) Gabe Monroy told me.
He also added that, because SMI provides the lowest common denominator API design, Open Service Mesh gives users the ability to “bail out” to raw Envoy if they need some more advanced features. This “no cliffs” design, Monroy noted, is core to the philosophy behind Open Service Mesh.
As for its feature set, SMI handles all of the standard service mesh features you’d expect, including securing communications between services using mTLS, managing access control policies, service monitoring and more.
There are plenty of other service mesh technologies in the market today, though. So why would Microsoft launch this?
“What our customers have been telling us is that solutions that are out there today, Istio being a good example, are extremely complex,” he said. “It’s not just me saying this. We see the data in the AKS support queue of customers who are trying to use this stuff — and they’re struggling right here. This is just hard technology to use, hard technology to build at scale. And so the solutions that were out there all had something that wasn’t quite right and we really felt like something lighter weight and something with more of an SMI focus was what was going to hit the sweet spot for the customers that are dabbling in this technology today.”
Monroy also noted that Open Service Mesh can sit alongside other solutions like Linkerd, for example.
A lot of pundits expected Google to also donate its Istio service mesh to the CNCF. That move didn’t materialize. “It’s funny. A lot of people are very focused on the governance aspect of this,” he said. “I think when people over-focus on that, you lose sight of how are customers doing with this technology. And the truth is that customers are not having a great time with Istio in the wild today. I think even folks who are deep in that community will acknowledge that and that’s really the reason why we’re not interested in contributing to that ecosystem at the moment.”
Powered by WPeMatico