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
The release of our book Actions in Action This was epic for Rob Bos, Michael Kaufmann, and me since we finally received the printed versions of our books. We spent about 18 months to get this book published. Last but not least, we got Scott Hanselman to write the foreword for our book; how cool is that!
It also fell short in supporting an engineeringculture of ownership and curiosity within the organization, exacerbated by the pricing model. Due to the high price per user, access to observability was limited to only senior members of the engineering teams. Book a consultation with our sales team.
Which makes sense of course, since two decades ago, building out the networking and compute capacity of the internet was one of the major engineering challenges of that period in the web’s history. It echos one of the key arguments of Fred Turner’s book, “ From Counterculture to Cyberculture.”.
Engineers are natural readers. They take enormous pleasure in learning about new things, and books are the perfect medium to cover complex ideas in depth. I picked some of my favorite books at my company, Semaphore — books that have profoundly influenced the company’s engineeringculture.
The book describes the C-level perspective on IT. During many conversations with customers, I experienced what the book describes: a C-level looks at IT in the same way. The last topic I would like to address is our main theme for the upcoming period: Creating EngineeringCultures for our Customer.
Honeycomb has played a pivotal role in this transformation, underscoring its importance in our journey towards a more sustainable and fulfilling engineeringculture ,” Josh explained. Book a consultation with our sales team. As people see these improvements unfolding, they gain confidence in the impact of their contributions.
Software Engineering at Google — a new O’Reilly book. Covers Google’s unique engineeringculture, processes, and tools, and how these aspects contribute to the effectiveness of an engineering organization.
principles of testing (popularized by the book Clean Code by Robert C Martin ). Tarlinder says a lot on testability in his book “ Developer Testing ” and provides good insights on what to look for. When writing tests, it is good to stick to the F.I.R.S.T These principles tell us our tests should be: Fast. Independent. Repeatable.
And it plans to add more than 1,080 new soft skills-related offerings this year, including live training courses, video courses, and books. “IT IT is not an individual sport,” says Laura Baldwin, president at O’Reilly Media. That might continue to work for a few rarified geniuses, he adds. But most of us are mere mortals,” he says.
” Recently, I read Kent Beck’s book “ Tidy First? The book thoroughly discusses the economics of tidying code. So if you’re trying to make a how-many decision (…) Break them down and think about them incrementally.” “, which I highly recommend.
to the release of our O’Reilly book, Observability Engineering , interest in the concept and practice of observability—as well as Honeycomb’s role in popularizing it—has taken off like wildfire. Enabling your team to work better together, through observability, is our ultimate goal.
When I joined CircleCI in 2018, the engineering team had been growing by 50 percent year over year, and also increasing in terms of geographical distribution. And after all this growth, we were running into challenges around evolving our engineeringculture. Conversely, the management team was incredibly small.
This book did not become a best-seller, but it did provide a summary of how lean principles work differently in automotive product development. For example, the book equates short production throughput time to short development lead time. If this sounds familiar, check out Mark Schwartz’s book War and Peace and IT. [15]
There’s a lot to say about refactoring, with many good books written on the topic. It usually involves taking hard-to-maintain, messy, or confusing code, and updating it to improve its readability and maintainability without changing its user-facing functionality.
Scott Page has famously demonstrated in books like The Diversity Bonus that teams with diverse experiences and “lower” individual aptitude perform better than homogenous ones where each individual is “better.” Management must create buffers which support the Center of Production Excellence if it deems these activities necessary.
That’s why I took on the task to build a Slack bot that could facilitate viewing, cancelling, and booking spots in the garage. 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. I build the Slack Bot using Block Kit.
The knowledge graph enabled us to better understand the trends of movies, TV shows, talent, and books. His favorite TV shows: Ozark, Breaking Bad, Black Mirror, Barry, and Chernobyl Since I joined Netflix back in 2011, my favorite project has been designing and building the first version of our entertainment knowledge graph.
The book covers many different engineering leadership roles and how one might work toward preparing for each. The post On Becoming a VP of Engineering, Part 1: The Path to VP appeared first on Honeycomb. And once you’re in the job, the requirements also don’t stay static, especially in a growing company.
It’s the Share Pie story in chapter 8 of Eric Evans’ DDD book. I hope you also enjoyed my highlights, but I would still recommend reading the whole story in the book. Software engineers are not typists who translate requirements into software. This treasure has been hiding in plain sight all along.
Our People (HR) team creates a Clubhouse ticket (project management software) that assigns tasks and due dates for everything ranging from granting the employee system access with IT to giving them branded swag to booking all their core meetings.
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. His theories notably influenced the Wachowski siblings’ The Matrix series, bringing some of his ideas into mainstream awareness.
“Honeycomb’s thought leadership aligned perfectly with our ethos, and we identified them as an ideal match from an engineeringculture standpoint,” shared Joel, adding, “ I firmly believe in the principle that a product should excel at one thing, and Honeycomb exemplifies that. Interested in learning more?
Thankfully, the book lays out guidelines about how to produce and accrue the greatest bonuses in various types of problems, like predicting or innovating. Each of these added to a group provides a bonus because it changes how the group can engage with the problem space, and they can also be combined to form synthetic methods of working.
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. The best thing is, this type of culture comes almost for free when you treat developers extremely well (as discussed previously).
What’s your favorite part about the engineeringculture (or company culture) at Netlify? On top of that, every Netlifolk has an education budget per year to spend on books, courses and webinars to further their professional development. Being able to have honest 1:1s with my manager and seeing results come from it.
And for me, the big part of the success of growth was actually a step above the pure engineering architecture. It’s firstly rooted in the engineeringculture because the first Netflix employees are great people. There are always some of the quantum principles that are cheaper and easier to follow in all scenarios.
Our guests today are two superbly experienced front end engineers, and with several books, and many, many talks between them. We have Rebecca Murphey, senior technical lead at Indeed.com, and Ben Vinegar, VP of engineering at Century. A company called Fresh Books. Thank you both so much for joining us today. Worked there.
I think Italian bus drivers used to do it and they would run exactly by the book and everything would take five times longer. There’s something called a work to rule strike, which I read about a couple of years ago and it’s hilarious. Ramin: They’re like, no, no, we’re doing exactly what you told us to do and it sucks.
My first question is in terms of this chaos engineeringculture, how does this play between your team with all the teams? If I have to wake up and run a run book, we’re already f *d. Audience: Hi, I actually listened to your previous talk about the Python script, to terminate using Lambda. Audience: Sure, sure, sure.
This is a big cultural shift! To help change the engineeringculture, weve defined a lot of skills around communication and teamwork. A new engineer is expected to participate actively in team conversations. As a reminder, what Im trying to do here is to change the engineeringculture at my company.
This book is an excellent read and it covers small things that you can do to build trust and to become an authentic and true leader to your team at different stages of your leadership journey. Book advocates that by focusing on the small things and executing them well, leaders can create a lasting impact on their teams and organisations.
Our existing deploy tooling and engineeringculture made the transition to remote work go much more smoothly. Though our deploy velocity remained the same, the engineering org has been far from stagnant. Another big effort from the DevRel team is Observability Engineering (a.k.a. the o11y book”).
Our existing deploy tooling and engineeringculture made the transition to remote work go much more smoothly. Though our deploy velocity remained the same, the engineering org has been far from stagnant. Another big effort from the DevRel team is Observability Engineering (a.k.a. the o11y book”).
If you’re interested in exec team dynamics and the craft of strategy, these three books have been particularly formative for our exec team: The Advantage : Why Organizational Health Trumps Everything Else in Business by Patrick Lencioni Good Strategy Bad Strategy by Richard P.
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