Xebia

AUGUST 3, 2021

Looking at the current technological and organizational paradigm, we can only recognize the world is massively different from 10 or 20 years ago. Gone are the days of making well-thought documents who are reviewed and tested by colleagues in the organization. Do you have the capabilities and time to guide the technical decisions?

Architecture 130

Architecture Organization Technical Review Software Review 130

CircleCI

MAY 26, 2020

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. It might only partially implement a feature (protected by feature flags or just not user-accessible), get reviewed, and get merged.

Software Review 132

Software Review Technical Review Engineering Culture Testing 132

Xebia

SEPTEMBER 14, 2021

Looking at the current technological and organizational paradigm, we can only recognize the world is massively different from 10 or 20 years ago. Gone are the days of making well-thought documents who are reviewed and tested by colleagues in the organization. Do you have the capabilities and time to guide the technical decisions?

Architecture 130

Architecture Organization Technical Review Software Review 130

Xebia

APRIL 5, 2022

If we were to take it one step further, where test automation is not only a tool to validate what we have made, but rather a way to write self-testing code , we find practices like Test-Driven Development (TDD). As Dave Farley and Arjan Molenaar wrote: “TDD is not about writing unit tests”.

Software Review 130

Software Review Testing Systems Review Technical Review 130

OverOps

JULY 11, 2018

The official definition of DevOps is “a software engineering culture and practice, that aims at unifying software development and software operation.” This can lead to frustration, a set back in deployment and high costs due to delays. They minimize and bridge the teams into one group, with a shared vision. . #3

DevOps 145

DevOps Software Review Systems Review Technical Review 145

Apiumhub

MARCH 3, 2022

Getting Stuff Done Days (GSDD) is an initiative used by many top companies to improve the quality of the software development and boost a proactive, continuous improvement-based engineering culture in their organizations. Be on top of the current trends and technologies and be able to apply them to benefit our clients.

Weak Development Team 59

Weak Development Team Software Development Software Review Software 59

CircleCI

JANUARY 22, 2021

While I have a lot of strong opinions on how to best bring automation to engineering teams, it’s clear that the most advanced, powerful automation tools need one crucial element to succeed: people. For businesses, the first phase of the pandemic was about systems: updating and building your tech stack so you could operate as fully remote.

Software Review 75

Software Review Software How To Technical Review 75

Honeycomb

JULY 12, 2023

Nonetheless, I think it’s useful to share what I can about my experience in the hope that it might encourage others to seriously consider this role, especially those from backgrounds, identities, and genders poorly represented in the VP of Engineering ranks today. The whole tech industry would benefit from more perspectives in this role.

Part-Time VPE 98

Part-Time VPE Engineering Technical Review B2C 98

Honeycomb

AUGUST 2, 2022

There’s also a strong debugging culture. There’s also a wonderful culture of documenting everything in living documents, so it’s easier to find things if I have questions. R : Multiple people have mentioned to me that it feels like they are able to start healing their scars from other tech companies when coming here.

Engineering 52

Engineering Technical Review Software Review Culture 52

Netlify

MARCH 2, 2021

At Netlify, we use a diverse set of technologies, languages and paradigms to build our product. These are built on three key principles: Automation : By automating recurring tasks whenever possible, we reduce the margin for human error and free up our engineers to focus on the right things. All flavors of it. Automated tests.

Software Review 70

Software Review Systems Review Technical Review Testing 70

Honeycomb

JANUARY 5, 2021

In March I wrote the following: Observability is a paradigm on which we can build a safe, healthy, sustainable future for the tech industry. A better tech industry is better for supporting this complex, interdependent society we live in. Though our deploy velocity remained the same, the engineering org has been far from stagnant.

Part-Time VPE 59

Part-Time VPE Technical Review Engineering Software Review 59

Netlify

SEPTEMBER 30, 2021

As an engineer based in the EMEA (Europe, Middle East, Africa), I usually start my work day earlier than folks in the Pacific time zone. So I tend to get as much work done as possible and also review PRs in the afternoons and then reserve the evenings for meetings/syncs with my colleagues. Pairing sessions also help a lot too.

Engineering 52

Engineering Technical Review Software Review Systems Review 52

Altexsoft

MARCH 3, 2023

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. In the meantime, a developer can work with a QA engineer to identify and fix the bugs or issues that pop up during testing. Software engineer.

Examples 52

Examples UI/UX Development Technical Review 52

Honeycomb

JANUARY 5, 2021

In March I wrote the following: Observability is a paradigm on which we can build a safe, healthy, sustainable future for the tech industry. A better tech industry is better for supporting this complex, interdependent society we live in. Though our deploy velocity remained the same, the engineering org has been far from stagnant.

Part-Time VPE 52

Part-Time VPE Technical Review Engineering Software Review 52

Strategic Tech

MAY 3, 2021

Protip: try to identify before the workshop if existing documentation exists so that you have time to review and prepare. Experiment and see what feels right as a starting point, and continuously review as you uncover more of the domain. Timeboxing and frequent, short retrospectives are valuable so that you can try things (e.g.

Software Review 52

Software Review Architecture Systems Review Technical Review 52

Honeycomb

APRIL 26, 2022

Any significant shift in an organization’s software engineering culture has the potential to feel tectonic, and observability (o11y for short)—or more specifically, Observability Driven Development —is no different. Technical context: cloud instance specifics, region/availability zone, etc. is something you may be thinking.

Weak Development Team 52

Weak Development Team Software Review Systems Review Real Estate 52

LaunchDarkly

JANUARY 14, 2020

That’s fascinating because it touches on so much of what you know and I’ve been in software engineering for a couple of decades now, a couple of days, decades, but sounds like couple of days. As the longer time you spend in it, the more you realize how much more it is about people than about technology. Maybe yes, maybe no.

Weak Development Team 10

Weak Development Team DevOps Testing Agile 10

LaunchDarkly

SEPTEMBER 20, 2019

I think it’s important when you’re talking about chaos engineering to also talk about culture. This still technically runs but it’s on its way out. There’s just a lot of lack of diligence, is what I’d call it, in our services. The failure scenario has become very complicated, very fast.

Engineering 9

Engineering Weak Development Team Development Team Review Testing 9

Hacker Earth Developers Blog

MAY 9, 2024

Industry and specialization: Specific industries may have their own preferred platforms or require niche features, such as technical skill assessments or industry-specific job boards. Are you filling high-volume roles, attracting experienced professionals, or seeking specific technical skills?

Recruiting 130

Recruiting Software Review Technical Review Software 130

Abhishek Tiwari

SEPTEMBER 15, 2024

Remember, while automation is powerful, it's still important to review significant updates, especially major version changes that might include breaking changes. The "how" of implementation is important, but it's typically well-documented in the code itself and associated technical documentation.

Engineering 59

Engineering Software Review Technical Review Weak Development Team 59

Honeycomb

APRIL 15, 2024

tool, Pax8 faced hurdles in fostering a culture of ownership and curiosity due to user-based pricing limitations and an impending steep price increase. Pax8’s platform engineering team was keen on modernizing the company’s cloud commerce platform, but they were hitting obstacles with their traditional observability 1.0

Engineering Culture 111

Engineering Culture Culture Engineering Software Review 111

LeanEssays

JULY 14, 2019

The implications were clear: Perhaps in the end the open-source culture will triumph not because cooperation is morally right…. So small changes were submitted, reviewed, and integrated into the live code base as quickly as possible. The earliest technical problems centered on how to store all that data, and then how to search it.

Software Review 91

Software Review Software Engineering Weak Development Team Continuous Delivery 91

Honeycomb

JULY 14, 2023

This is particularly hard on engineering teams, where we always have to balance multiple priorities: security, reliability, performance, UX, shipping new features, iterating on existing features, internal developer experience, maintainability/tech debt, quality, scaling, etc.

Part-Time VPE 98

Part-Time VPE Engineering Weak Development Team Energy 98