As an architecture lead at Workiva, I’ve come to realize that technical problems are rarely, if ever, the reason for a project failing. Communication problems, on the other hand, can doom projects to failure from the start. Learn how we counteract these problems using Requests for Discussion (RFDs) to make scalable decisions.Keep reading.
One-on-ones are important to our culture at Workiva, with many different expressions depending on several factors. This post sheds light on adding value to these meetings.Keep reading.
Learn the eight steps of the software architecture process and how a software architect should act as a bridge between business stakeholders and technical stakeholders.Keep reading.
Workiva recently helped sponsor a charity event called dsmHack. It was both fun and fulfilling, and we would like to tell you a little bit about our team's experience—what we made and how we pulled it off.Keep reading.
Learn about the the role and daily responsibilities of an Software Development Engineer in Test (SDET) at Workiva. What does a SDET do and what are some of the common misconceptions?Keep reading.
Workiva engineers volunteered to help out the next generation of programmers. Read the blog to see highlights from Kids Code Summer Camp.Keep reading.
Find out what valuable lessons one Workiva intern has learned while beginning his engineering careerKeep reading.
Let’s face it. We’ve all been there.
Trapped in a meeting that seems to be going nowhere, while the team on the other end of the call dominates the entire conversation. And, isn’t this the fourth time this month you’ve discussed this very issue?Keep reading.
Building reliable systems is a key part of the engineering process at Workiva.Keep reading.
Code reviews are more than just a chance to catch bugs before they reach production. They are a mentoring opportunity to spread knowledge and improve our teams and code. Every code review should have two outcomes: improved code and improved engineers.Keep reading.