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!
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.
If you add a culture in which we continuously help each other by focusing on what we can still improve, that sometimes can become a bit scary. 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 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.
.” A paradigm shift towards sustainable excellence Honeycomb was instrumental in transforming the engineering landscape at Amperity, moving away from the “old school” engineering characterized by grueling weeks and overnight pages for support that often led to burnout. Book a consultation with our sales team.
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. Combat hero culture and fix structural issues.
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.
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.
Because of this, it’s especially rewarding for Honeycomb to be recognized recently for the work we do within our metaphorical walls, with Comparably naming us in over ten different categories , including “Best Company Outlook,” “Best Company for Diversity,” “Best Leadership Teams,” and “Best Company Culture.”
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.
” 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.
The knowledge graph enabled us to better understand the trends of movies, TV shows, talent, and books. The company was intriguing to begin with, but I knew nothing of the talent, culture, or leadership’s vision. After interviewing, it became clear to me that this company culture was different than any I had experienced.
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. Sergey: I think I would respond with sort of a catchy phrase from our Netflix culture deck.
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. So, by day one, they have three key people to talk to: Ops, a buddy, and their manager.
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.
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 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.
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. As a business, the economics of this type of culture should tell you everything. There is a bigger pool of candidates?
What’s your favorite part about the engineeringculture (or company culture) at Netlify? Ownership and trust are some of the best features of our culture for me. On top of that, every Netlifolk has an education budget per year to spend on books, courses and webinars to further their professional development.
At the start of lockdown, many companies doubled down on their butts-in-seats culture with Zoom surveillance and other creeptastic endeavors. Our existing deploy tooling and engineeringculture made the transition to remote work go much more smoothly. Another big effort from the DevRel team is Observability Engineering (a.k.a.
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.
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.
“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?
At the start of lockdown, many companies doubled down on their butts-in-seats culture with Zoom surveillance and other creeptastic endeavors. Our existing deploy tooling and engineeringculture made the transition to remote work go much more smoothly. Another big effort from the DevRel team is Observability Engineering (a.k.a.
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.
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.
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 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? If I have to wake up and run a run book, we’re already f *d.
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.
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.
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
The implications were clear: Perhaps in the end the open-source culture will triumph not because cooperation is morally right…. They have a culture of respect for engineers, and of long-term thinking. For example, the book equates short production throughput time to short development lead time.
Framed by Kalanick as his “revenge business” after his previous P2P startup Scour was sued into oblivion for copyright infringement, Red Swoosh would be the precursor for Expensify’s future culture and ethos. It echos one of the key arguments of Fred Turner’s book, “ From Counterculture to Cyberculture.”.
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