DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Latest Articles - DZone

article thumbnail
Spring Boot Secured By Let's Encrypt
In this post, learn how to use the Let's Encrypt tool with Spring Boot to generate HTTPS certificates and automatically renew them.
Updated February 16, 2022
by Emad Heydari Beni
· 136,359 Views · 24 Likes
article thumbnail
Getting Started With Apache Cassandra
In this hands-on primer on the powerful open-source NoSQL database Apache Cassandra, our discussion includes the CAP theorem and how to structure data.
February 16, 2022
by David Jones-Gilardi
· 7,830 Views · 3 Likes
article thumbnail
Polymorphism, Encapsulation, Data Abstraction and Inheritance in Object-Oriented Programming
In this article, we discuss four central concepts in Object-Oriented Programming, including Polymorphism, Abstraction, inheritance, and Encapsulation.
Updated February 16, 2022
by nick flewitt
· 8,249 Views · 2 Likes
article thumbnail
Strict Validations in Mulesoft APIkit Router
This article will help you in your understanding of the functionality of Query Parameters and Headers Strict Validations in the MuleSoft APIkit Router.
February 16, 2022
by Abhishek Bathwal
· 10,387 Views · 2 Likes
article thumbnail
The Four Pillars of Mobile DevOps Strategy
As the need for adopting mobile-specific processes for mobile apps, the following four key components help teams define a strategy with metrics that deliver results.
Updated February 16, 2022
by Nora Bezi
· 39,296 Views · 9 Likes
article thumbnail
Completed Staff Work: Making Recommendations vs Asking for Approval
When I was introduced to the concept of Completed Staff Work, I felt like I had been handed a secret management technique. I had been a manager for several years and never heard of it, so it felt like a big secret when I did. And the idea simply exploded how I thought of my work as a leader. So, let me share with you one of the most powerful management concepts I’ve encountered: Completed Staff Work. A standard for determining whether or not you’ve done enough work on a problem, the concept of Completed Staff Work involves useful techniques to Assume more autonomy for your team Prevent going back and forth endlessly on topics, and Carve out greater responsibilities for yourself. An Example of Typical Staff Work New Relic had a couple of engineers located in a coworking space in a city in Europe. They were unhappy with the location—it had no windows, and they said it felt too tight. I talked about the issue with our facilities person, and he quickly located another location for us. But to make it happen he needed email approval from my manager. I composed an email to my manager that read something like this: We’ve located a larger location. Their current office is cramped and has no window. The new office has a window, and enough room to fit 3 or 4 desks. The team looked at it and said it was perfect for their needs. If you approve, reply to this email with approval for the additional monthly expenditure of $X a month. That seems pretty straightforward, right? But it’s worth thinking for a moment about what is incomplete about this work—why this is incomplete staff work. Incomplete Staff Work My work was not complete, because my manager still had questions: We have another office in that area. What would the impact be of merging the two offices? What is our company policy for coworking spaces? Do we have some standards, so that we’re not treating some locations poorly and others better? Will we need more room to grow in this office? What are our future plans there? How does this space compare to other coworking spaces we’re using? How much space do they have now, and what would help them to do their best work? What typically happens with Incomplete Staff Work is the Great Going Back and Forth: Lots of questions flying around, lots of time spent figuring things out. If there are multiple levels of approval, Incomplete Staff Work can be incredibly tiresome. A couple of takeaways: That back and forth may indicate that I haven’t thought about things completely enough. Usually, the problem is that I haven’t considered the bigger picture: how a particular change would affect the rest of the company. The other problem is that I hadn’t really dug into the important details. When I asked the facilities person how much space they recommended, it came to light that the engineers had half that recommendation per person. That provided a compelling argument for improving their location. What Is Completed Staff Work? Completed Staff Work is when you present your plan to a decision-maker, and they can just give it a thumbs up to approve it. If they say, “sounds great, do it!” then it’s Completed Staff Work. One way of thinking about Completed Staff Work is this: Are you providing your best recommendation? Is it something you would stake your professional reputation on? If it isn’t, then it’s not Completed Staff Work. So to take the earlier example, a better example of completed staff work would read something like this: I’ve looked into the alternate location for the London engineering team, and recommend that we go with a larger location the head or real estate located. Here’s some context for the recommendation. If you approve, reply to this email with approval for the additional monthly expenditure of $X a month. And let me know if you have concerns or questions. The current London engineering location is half the square footage per person that our real estate person recommends. It doesn’t meet our standards for coworking facilities and is the least square footage per person of all of our facilities around the world. He recommends we either go with the new coworking facility, which is cost-effective for that area and size or have them move into the London office with the rest of the sales team. I explored having the engineering team be part of the London office, but it’s over an hour away from their homes. I’ve discussed it with them and we agreed to do a two-week trial — that trial just ended and they felt it was untenable to commute that distance. The new location I’m recommending is a little larger than our current plans for the team. We’re not planning to add more people to the London engineering team over the next year. But this does preserve some optionality in case we change our mind, and other places in the area were more expensive for less square footage. The team members are critical to the success of our XYZ product, and as you know the team has been vocally unhappy with the current location. I believe this is directly tied to their productivity and retention. The expenditure is still well within the normal range for other coworking facilities, so I recommend we use it and move the team as soon as possible. See how different that is? I’ve thought of all the things my manager may care about. I really own the problem and have thought about it from a company-wide perspective. No back and forth is necessary. Completed Staff Work Flattens Hierarchy As humans, we are used to asking our boss to make the decisions. Many organizations actually discourage people from providing plans and decisions for ratification, because it’s acting more like an equal to your manager, and organizations typically, if unconsciously, like to reinforce hierarchy. In this case, once I noticed that my manager had a lot of questions, I put together a more complete plan with a lot more context. This required me to ask more questions of our facilities person and do more legwork. I thought about the questions my manager might have, which helped me think about the problem more holistically. Doing this deeper work made me feel like I owned the solution more deeply. There was a switch in my relationship with my manager. Instead of me asking him for approval, I was making a recommendation that had everything he needed to know it was a good choice. I knew it was Completed Staff Work after I had done that extra work because I knew it was a good decision—one that I would stake my reputation on. But it was proven to be Completed Staff Work when he not only gave it a thumbs up, but passed it to his manager for approval, and his manager approved it without comment. Complete! It’s much more useful to bring your intention and best thinking to the conversation, rather than relying on your manager to decide whether something is a good idea or not. This inverts the way you relate to your manager—and to me, that’s the real power of Completed Staff Work. Completed Staff Work Is a Structure to Empower Teams Completed Staff Work became prominent in the U.S. Army in the 1940s. Although derived from a hierarchical, written process, the principles are broadly useful and can be adapted to many situations. Completed Staff Work empowers teams to have more local autonomy. Instead of relying on the manager to decide on the best course of action, the team members are bringing their best solutions to the manager. The manager may provide clarification or guidance when they’re missing something, but over time the team will develop a habit of solving problems in a more organizationally aware way. This leads to them needing less meddling from above, and having more local decision-making. Completed Staff Work Can Be Quite Simple The simplest form of Completed Staff Work is simply stating an intended course of action in the form of “I intend to do X.” That establishes and takes ownership of the course of action you intend to follow. If the decision-maker has questions about that course of action, they can ask. But many problems are more complicated. For example, you can’t create a huge shift in the company’s strategy merely by saying, “I intend to do X,” because so many people may need to get on board with the new strategy. That’s when it can make more sense to write it down, and have many conversations to get people aligned on it. Both approaches are a type of Completed Staff Work. Completed Staff Work Can Be Iterative Sometimes people interpret Completed Staff Work to mean that you shouldn’t show work that is in progress, revealing it only when you’ve perfected it. But the goal of Completed Staff Work isn’t to do everything as one chunk or to produce a work artifact. The goal is to do the work in a way that has been thought about deeply enough that your stakeholders should be able to accept your recommendation, and know that it is a good decision. It’s often a good idea to talk with your decision-makers as you’re putting together your plan. Ask them what a good plan will look like, and run the outline by them. If you need their help, ask. That’s what they’re there for. To make Completed Staff Work more iterative, I’ve found it useful to approach it as a set of smaller pieces of staff work. Let’s say our team’s section of the website is performing worse each week. Here’s what I might say to my manager: “The performance on the site has been getting worse and worse, and I intend to put together a plan to address it. Sound good?” This can be a good time to talk about the parameters of the work you’re doing. If the problem is simple, I can stop there. But for more complex problems, I may need them to agree with the outline of the plan, and then go actually do the work of putting together the full plan. I may have to talk to a lot of people to figure out the best thing to do. And if the problem is really difficult, I can give my best approximation of a plan, and ask for help completing it. After having those conversations and doing that homework, I’ll either verbally tell my manager the plan and make sure they agree with it, or show them a written version: “Our plan to address the recent site performance issues is to set up a dashboard in our office area, and to set up the New Relic performance alert email to go to the whole team. We’re also planning to focus on fixing three performance issues next week. Sound good?” If you get a “looks great, go for it,” then you know you’ve done Completed Staff Work! But you’ve also done it iteratively, and your manager has the chance along the way to say, “No, don’t work on that, because somebody else is actually taking care of that right now.” What’s Better Than Completed Staff Work? When I started as a manager, my colleagues recommended a book called Turn the Ship Around: A True Story of Turning Followers Into Leaders. It tells the story of the USS Santa Fe, a submarine with one of the poorest performing crews in the fleet. Captain David Marquet switched the ship’s culture from the leader telling people what to do, to individuals sharing their thinking and making decisions themselves. Marquet points the way to something even better than Completed Staff Work. He does this by describing a progression in how people talk, from being a follower to being a leader: Tell me what to do I think… I recommend… I request permission to… I intend to… I’ve done… I’ve been doing… Completed Staff Work is a structure to get people to the “I recommend,” “I request permission to,” or “I intend to” phases. But you don’t have to stop there. If your team members are doing Completed Staff Work, you should consider whether they should have to ask you to “thumbs up” it at all. Pushing responsibilities farther down the spectrum leads to better results, as long as the people involved have the skills and support to succeed. One way to evaluate whether they are ready is to monitor how they’re doing with their existing staff work. If their work typically just requires a “sounds great,” consider giving them more authority to make those decisions without you. On the other hand, situations in which you aren’t able to give the go-ahead represent a coaching opportunity. What did they miss and why did they miss it? Did they lack a key skill or background? Do they need more support or time to think about the problem? Did you give them the right context to be successful? It’s a great opportunity for learning. I hope you find Completed Staff Work as useful as I have. I welcome your feedback.
Updated February 16, 2022
by Jade Rubick
· 13,373 Views · 4 Likes
article thumbnail
Using Travis CI for Deploying Mulesoft Applications to Cloudhub
This tutorial explains what Travis CI is and how you can use it to deploy Mulesoft applications to Cloudhub. Read below to find out more!
February 16, 2022
by Kuldeep Rana
· 10,833 Views · 2 Likes
article thumbnail
Do AI Bots Need Some Regulations?
Well, do they? Let's look at fundamental policies, data privacy and security, handling rogue chatbots, and dealing with moral issues.
Updated February 16, 2022
by Amaan T
· 8,161 Views · 4 Likes
article thumbnail
5 Best MySQL Courses for Beginners and Experienced Programmers
A developer shares five courses that can help you learn SQL and MySQL. Find the right online course to learn MySQL database concepts and commands in-depth.
Updated February 16, 2022
by Javin Paul
· 24,611 Views · 10 Likes
article thumbnail
Win Your War Against Hackers and Secure Your Network
With hackers becoming more active every year, it's more important than ever to insure proper security practices in your organization. Read on for some practical tips.
Updated February 16, 2022
by Giridhara Raam
· 8,309 Views · 5 Likes
article thumbnail
Learn From Netflix, Stack Overflow, Slack, and More
A free virtual event on April 7th, INTERACT will have over $30 billion in engineering wisdom on display - and DZone is a proud sponsor.
February 16, 2022
by Dan Lines
· 11,819 Views · 7 Likes
article thumbnail
What Is BizTalk Server?
A developer discusses what makes BizTalk server a great middleware for integration, and how it works to receive, orchestrate, and send messages.
Updated February 16, 2022
by Kamlesh Kumar
· 23,201 Views · 8 Likes
article thumbnail
Why the Cool Kids Use Event Loops
Follow a discussion on the benefits of event loops in Java and learn why if it was good enough for the old-timers, maybe it's good enough for us today.
February 16, 2022
by Rob Austin
· 4,864 Views · 10 Likes
article thumbnail
How to Write a Software Requirements Specification (SRS) Document
An SRS document describes the yet-to-be-developed software system. It's accessible to all parties, including the stakeholders, programmers, designers, etc.
February 16, 2022
by Anastasiia Komendantova
· 4,633 Views · 3 Likes
article thumbnail
Making 3D CSS Flippable Cards
In this tutorial, we will look at all the JavaScript and CSS required to make 3D, interactive, flippable cards, which look great in any application.
February 16, 2022
by Johnny Simpson
· 4,074 Views · 4 Likes
article thumbnail
Understanding OpenJDK and Why You Should Use It
In this article, we will try to answer this question by reviewing the process of constant upgrading of OpenJDK and its open-source approach to development.
February 16, 2022
by Dmitry Chuyko
· 5,297 Views · 4 Likes
article thumbnail
Using Azure Load Balancer With CockroachDB
Today, we'll set up Azure Load Balancer service with CockroachDB. Our docs have a note on it but I'll attempt to fill in the blanks of setting up ALB.
February 16, 2022
by Artem Ervits DZone Core CORE
· 7,399 Views · 3 Likes
article thumbnail
10 Tips To Optimize Angular Application To Increase Website Speed
Angular is known for its feature-rich, high-performing characteristics as a front-end framework. In this post, I'll share how to optimize Angular application performance.
February 16, 2022
by Kiran Beladiya
· 4,015 Views · 3 Likes
article thumbnail
Apache Beam Working With Files
The article explains how to read, write data to and from the file in Apache Beam with a pipeline where the ‘Employees.csv’ file be read/filtered/write to a new file.
February 16, 2022
by Sameer Shukla DZone Core CORE
· 8,855 Views · 3 Likes
article thumbnail
Microservice: Creating JPA Application Using Jakarta Persistence API in Payara Micro
In this blog, we will discuss how your Java microservice application can connect to and interact with a relational database through the Jakarta Persistence API.
Updated February 16, 2022
by BUHAKE SINDI DZone Core CORE
· 6,061 Views · 4 Likes
  • Previous
  • ...
  • 753
  • 754
  • 755
  • 756
  • 757
  • 758
  • 759
  • 760
  • 761
  • 762
  • ...
  • Next
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook
×