ServiceNow

1 Crucial Trait every Great ServiceNow DEVELOPER MUST HAVE...

Lukasz Szumilas

26 Oct 2023 — 3 min read

What's the one trait that separates good developers from great ones?

Let's dive in.

The rule is simple, the more responsibility you are willing to take the higher you will go.

After all, people that are in high position, are there because they are responsible for:

1. Bigger things

2. More people than themselves.

People often confuse responsibility.

They think responsibility is admitting it is their fault.

Even if something is not your fault it is still your responsibility.

Lets see some real life examples.

Certainly, some people write descriptions better than others.

IIt's not your fault that the story lacks a clear description.

Even so, it's your responsibility to find the information you need and provide a high-quality solution.

Certainly, there should be a person that tests your solution and they should make sure there are no bugs.

It's not your fault that someone didn't test the solution.

Even so, it's your responsibility to ensure your solution works well and doesn't cause any regression.

Certainly, if you have written to someone they should give you an answer.

It’s not your fault that story is not progressing because you lack answer.

Even so, it’s your responsibility to try to find a way to get information, as you are responsible for a story.

Certainly, You should stick to what the story outlines for delivery.

If the client leaves out critical information, that's not your fault.

Even so, it’s still Your responsibility to provide a solution that meets the client's actual needs, which may not always align with their wants.

Managing Workload:

It's important for developers to be responsible but also to recognize their own limitations. Overcommitting can lead to burnout and negatively affect the quality of their work.

Embracing Errors:

Being responsible doesn't mean living in fear of making mistakes. Errors are inevitable, even for seasoned developers. The important thing is to acknowledge the mistakes, learn from them, and correct them.

Taking responsibility empowers you to:

Fix mistakes
Learn
Ultimately become invaluable.

Always have in mind that in order to be great developer you should take extreme responsibility for everything you work on.

ServiceNow API A Restaurant Analogy

The restaurant represents a software system with an API. Just like a restaurant prepares and serves a variety of dishes, the software offers different services or data. The waiter in the restaurant acts like an API. You tell the waiter (API) what you want (your request), and the waiter goes

ServiceNow CSDM vs. CMDB A City Analogy

At its core, the CSDM (Common Service Data Model) is a framework or guideline for how to structure data in your ServiceNow environment. Think of it like the scheme for a city. Just as a city sheme would outline where to place: * residential areas * commercial districts * parks * roads * utilities The

ServiceNow Scoped Application vs. Global Application: A Shopping Mall Analogy

Welcome to the ServiceNow Mall Imagine a mall with different stores and one central security office that oversees the entire mall. Scoped Application Each store in the mall is like a scoped application. It operates independently, has its own staff (users), rules (permissions), inventory system (tables), and cash registers (interface)

Keep your Prod-Test-Dev instances aligned.

Why? 💡 It is crucial for maintaining consistency and control over your processes. What does that mean? 🤔 Lets see on real life scenario: You implement a script to add 100 new groups with different names, but similar configuration. You run the script on Developer Instance and the table gets populated. Then