CircleCI

JANUARY 22, 2021

The rollercoaster of 2020 highlighted the competitive advantage that well-oiled software delivery teams provide. The minute COVID-19 hit and everyone had to become not just remote-first, but remote-only, many engineering teams were forced to reckon with the number of manual processes they had in place. Where is it going to tip over?

Software Review 75

Software Review Software How To Technical Review 75

CircleCI

MAY 26, 2020

The path of a software engineer is one of constant learning. 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. CircleCI showed me that I had still more to learn.

Software Review 132

Software Review Technical Review Engineering Culture Testing 132

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. Using common software, functionalities can be purchased and integrated with the click of a button and the availability of a credit card. Do we need architects anyway?

Architecture 130

Architecture Organization Technical Review Software Review 130

Honeycomb

FEBRUARY 9, 2021

I’ve got a ton of personal reasons for joining Honeycomb that may not be worth being all public about, but after thinking for a while, I realized that many of the things I personally found interesting could point towards attitudes that result in better software elsewhere. Someone who can work in both software engineering and automation.

Technical Review 138

Technical Review Software Review Systems Review System 138

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

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.” The concept of Site Reliability Engineer (SRE) has been around since 2003, making it even older than DevOps. 3 Implement Gradual Change.

DevOps 145

DevOps Software Review Systems Review Technical Review 145

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

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 B2C Technical Review 98

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.

Software Review 76

Software Review Systems Review Technical Review Testing 76

Netlify

SEPTEMBER 30, 2021

Running untrusted code in-process and ensuring it doesn’t spend too long executing and doesn’t block the whole process. 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. Ownership and trust are some of the best features of our culture for me.

Engineering 52

Engineering Technical Review Software Review Systems 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. This is why we highly encourage all teams to instrument their code to emit telemetry data. .

Weak Development Team 52

Weak Development Team Software Review Systems Review Real Estate 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. No Q4 code freezes for us. no oversharing or prying).

Part-Time VPE 57

Part-Time VPE Technical Review Engineering Software Review 57

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. No Q4 code freezes for us. no oversharing or prying).

Part-Time VPE 52

Part-Time VPE Technical Review Engineering Software 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. For example, the UX designer may closely work with the developer to ensure the software’s interface is user-friendly.

Examples 52

Examples UI/UX Development Technical Review 52

Strategic Tech

MAY 3, 2021

Mapping out your business’s domain landscape has many benefits: knowledge sharing, generating product ideas, providing the foundation for software architecture, aligning on requirements, but a common challenge is… “where do we start?” business, software, teams), it’s discovery structure. Q: What if the high-level structure is wrong?

Software Review 52

Software Review Architecture Systems Review Technical Review 52

LaunchDarkly

JANUARY 14, 2020

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. I did a bunch of stuff at different code paths.

Weak Development Team 10

Weak Development Team DevOps Testing Agile 10

LaunchDarkly

SEPTEMBER 20, 2019

It can be network latency, network flapping, buggy software. 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.

Engineering 9

Engineering Weak Development Team Development Team Review Testing 9

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 109

Engineering Culture Culture Engineering Software Review 109

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

LeanEssays

JULY 14, 2019

Lean was introduced to software a couple of decades ago. The Nature of Software “Do not go where the path may lead, go instead where there is no path and leave a trail” -- Ralph Waldo Emerson It’s May 27, 1997. I show that these models derive from opposing assumptions about the nature of the software-debugging task.

Software Review 91

Software Review Software Engineering Continuous Delivery Technical Review 91