This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
In my experience, the culture is better and the results are better in orgs where engineers and architects obsess over the design of code and architecture. In orgs where it’s all about delivering tickets as quickly as possible or obsessing over technology, the culture and results are poorer.
InnerSource can be defined as the application of open-source softwaredevelopment principles within an organization’s internal softwaredevelopment processes. It draws on the valuable lessons learned from open-source projects and adapts them to the context of how companies create software internally.
Code review is a key step during the softwaredevelopment process — it’s when people check a program by viewing and reading parts of the source code. But despite its importance, not all developers are pleased with the way traditional code reviews work. Pulse aims to help in this process.”
If you have been in a scrum team (or even an agile softwaredevelopment team), you most certainly have had or heard about sprint retrospectives or gone through them. The post How to Rethink Sprint Retrospectives to Shape a Better Culture appeared first on DevOps.com.
It’s well-established that there’s a severe shortage of experienced softwaredevelopers. In a February poll by Infragistics, more than half (53%) of softwaredevelopers and IT professionals said that the biggest challenge this year will be recruiting developers with the right skills.
Because we know engineering wants to take care of their people, Allstacks has a whole set of features and metrics geared toward keeping a pulse on the team and supporting healthy engineeringculture. Read more about the impact of Covid-19 on softwaredevelopment.
Being on the leading-edge of softwaredevelopment requires quality observability insights, and the company wanted a new partner that could support their engineering charter for continual improvement and growth. The challenge? As people see these improvements unfolding, they gain confidence in the impact of their contributions.
The founders were immersed in XP, and XP is where we want to return, but there was a period of time where the company grew quickly and lost that XP culture. We have a bunch of engineers who dont have the XP mindset. This is a matter of changing organizational culture, and organizational culture isnt easy to change.
Getting Stuff Done Days (GSDD) is an initiative used by many top companies to improve the quality of the softwaredevelopment and boost a proactive, continuous improvement-based engineeringculture in their organizations. This year Apiumhub is implementing this approach as well. Getting Stuff Done Days (GSDD).
Before joining CircleCI, my years of experience led me to believe that I was an engineer with a firm understanding of the technical aspects of the craft, as well as what is considered good practice. At CircleCI, my team uses a short-lived branching model for softwaredevelopment.
Is collaborative softwaredevelopment enough? DevOps changed softwaredevelopment – whether cloud-native, cloud-hosted or “Oops! It goes beyond just engineeringculture and draining the backlog using harmonious collaboration. Let’s look at how we know how well we are doing that.
This article presents how to use data science to detect wastes and impediments, and concepts and related information that help teams to figure out the root cause of impediments they struggle to get rid of.
The official definition of DevOps is “a softwareengineeringculture and practice, that aims at unifying softwaredevelopment and software operation.” In order to better communicate and build better products, DevOps became one of the most critical positions in every company.
When I joined Discover® Financial Services in 2021, the company was executing its Runway: Mission 80,000 Feet vision to transform the engineeringculture toward product-centricity. We came together as one team across the organization to create a culture of continuous learning, knowledge sharing, and improvement.
You need two things to effectively move fast: a culture of psychological safety and smart investments in tooling. The culture and tools are part of the equation; the final piece is having the right processes in place to effectively use the tools and support the people. Setting yourself up for success.
As a softwareengineer or individual contributor, the next step in your career can be to become a principal engineer. The path to becoming a principal engineer at companies can feel unclear, which can inhibit individual engineering careers.
Will it help us improve how we think about modeling developer productivity? ” When I think about softwaredevelopment activities and their opportunity costs, I think of the choices we make on a product level. A development team can be very productive in terms of output, e.g., delivering several features quickly.
I’ve been quiet lately, and that’s because I’ve joined OpenSesame as Vice President of Engineering. It’s been a fascinating opportunity to rebuild an engineering organization from the inside, and I’m loving every minute. What I’m really doing is changing the engineeringculture at OpenSesame. It tends to snap back.
I picked some of my favorite books at my company, Semaphore — books that have profoundly influenced the company’s engineeringculture. This list contains a mixture of classic, timeless texts and a fair share of modern game-changing publications, aimed at senior engineers and devs.
As Smale explains, “Our engineeringculture is open and centered around teams owning services and being responsible for running them in production.”. It’s undeniable that open source has changed the way we all build software. It’s how people build proprietary software across industries, teams, and time zones.
We build teams hoping to do that 1-5% and giving little attention to the rest, then wonder how to fix that culture. Initially, as a softwaredeveloper, it’s tempting to frame the software as an independent system that you work on. — Fred Hebert (@mononcqc) August 5, 2020.
In the user acceptance phase of software testing, developers provide part or all of the application to end-users or their representatives to model real-world interactions and functionality. Many healthy engineeringcultures avoid relying heavily on user acceptance testing due to its unreliability, cost, and time consumption.
The pressure on today’s development teams is real: innovate, release quickly, and then do it all again, only faster. Is it any surprise that studies are showing 83% of softwaredevelopers are feeling burnout? Observability is more than a platform: it’s a culture shift.
Think in terms of modern softwaredevelopment which mostly involves receiving data, transforming it, and sending it to the next part of the system. T he simpler it is to explain , the simpler it is to understand. Any ambiguity in the requirements will lead to ambiguity in the implementation.
Here I would like to share with you the outcomes of the “Path to Principal: Defining the Modern Principal Engineer” panel discussion that I had a chance to attend. So, in this article, you will find common patterns as well as our definition of Principal Engineer based on our experience. is not just about softwaredevelopment.
The 1981 book Simulacra and Simulation by Jean Baudrillard is widely read and cited within academic circles but also permeates popular culture, influencing films, literature, and art. In the context of softwaredevelopment, particularly with observability 1.0’s
PDF) Culture Changes The purpose of the new career ladder is to help change the engineeringculture at OpenSesame. PDF) Here’s a summary of the titles and skills, with changes marked: Associate SoftwareEngineer Associate SoftwareEngineers are just starting their softwaredevelopment careers.
We are still in mid-journey but we can share a few highlights of what we have learned so far: The Netflix culture played a key role The Netflix engineeringculture famously relies on personal judgement rather than top-down control. Softwaredevelopers have both freedom and responsibility to take risks and make decisions.
If you like the ideas in the post, then why not come and join me at Navico and help us to build a highly-innovative engineeringculture and a brilliant place to work. this company is highly bureaucratic and it’s probably hard for developers to do any interesting or innovative work here. Not all code is created equal.
In this article, Tariq King describes the metaverse concept, discusses its key engineering challenges and quality concerns, and then walks through recent technological advances in AI and software testing that are helping to mitigate these challenges.
A defective softwaredevelopment process, for instance, may appear to be reducing the overall number of bugs reaching the users, but the driving cause of the decreases might just be the throttling of the development effort. For software, picking a good process is crucial.
Machine learning is a powerful new tool, but how does it fit in your agile development? Developing ML with agile has a few challenges that new teams coming up in the space need to be prepared for - from new roles like Data Scientists to concerns in reproducibility and dependency management. By Jay Palat.
Recently at Xebia, a new office location opened up in Amsterdam. At this location there is only a limited number of parking spots, and we want to avoid colleagues arriving at the office with their car without an available spot to park.
My favorite jobs have all been wrapped in a strong engineeringculture; one that strives to always do the right thing, pay attention to the details, avoid politics and focus on getting the best quality possible. Most of them were dominated by horrible people or bad cultures. It still does. Life is tough.
Any significant shift in an organization’s softwareengineeringculture has the potential to feel tectonic, and observability (o11y for short)—or more specifically, Observability Driven Development —is no different.
I landed deep in the heart of a reasonable engineeringculture. Some people on the outside might have confused that development process with a classic waterfall one, but it wasn’t really. If you boil it down again and again, softwaredevelopment keeps coming back to its roots in engineering.
For this, companies need to carefully design their teams, set clear goals and processes, and cultivate the culture of mutual trust and communication between employees with different expertise. Here, we will focus on softwaredevelopment so the roles will be chosen correspondingly. What is a сross-functional team?
The cost of these small domain-related changes (like renaming, and extracting parts of code) is so little that it should be a good habit of every professional developer. In this story, the engineers and project manager decided to be bold and spend the time improving the model at the risk of missing a deadline.
I think it’s important when you’re talking about chaos engineering to also talk about culture. My first question is in terms of this chaos engineeringculture, how does this play between your team with all the teams? My SRE team looks more like a softwaredevelopment team than it looks like assisted team.
At the November Test in Production Meetup in San Francisco, LaunchDarkly’s Yoz Grahame (a Developer Advocate) moderated a panel discussion featuring Larry Lancaster, Founder and CTO at Zebrium, and Ramin Khatibi, a Site Reliability Engineer (SRE) and infrastructure consultant.
What is engineering excellence? Engineering excellence, in the context of softwaredevelopment, is the relentless pursuit of quality, efficiency, and effectiveness in every aspect of our work. Each individual action might seem minor, but together they create a robust, secure, and efficient development process.
Open Source and a Culture of Sharing. The rise of open source software in the 1990s has undoubtedly transformed IT. While vendor lock-in is still a very real issue, the availability of open source software has done a lot to liberate IT. That’s where you should focus your softwaredevelopment effort.
I then make a sustained argument from the Linux experience for the proposition that “Given enough eyeballs, all bugs are shallow”, suggest productive analogies with other self-correcting systems of selfish agents, and conclude with some exploration of the implications of this insight for the future of software.
This tries to set up a base understanding of characteristics that make up a healthy EngineeringCulture. Psychology values Team Pyramid. It’s an analogy to the Maslow Hierarchy of Needs. Related to the “Psychological Safety rated as the common in successful teams” Learned it in a session facilitated by Amy.
We organize all of the trending information in your field so you don't have to. Join 49,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content