Clean Implementation

We can learn so many things from software development and architecture principles. In software development, writing clean code is crucial; if you are a software developer, you would 100% appreciate the importance of clean code.

You might argue that the word ‘clean’ is a bit arbitrary here and what makes a code clean? Another thing you might say is that ServiceNow is a kind of low-code or no-code platform, so how is this applicable?
Let us look at the tenets of clean code and see how we can apply this to our ServiceNow implementation.

Tenets of Clean Implementation
Continue reading →

Understanding Semaphore

like many ServiceNow pros, Semaphore comes to mind when there is a performance issue, however, Semaphore is much bigger than that. here I am trying to learn more about Semaphore.

What is Semaphore?
according to ServiceNow docs and JVM docs, Semaphore manages and protects ServiceNow resources and limits the number of activities for a specific resource. Semaphore does that by controlling transaction queues in a first-in-first-out fashion(FIFO).

Continue reading →

What does ServiceNow Architect do?

When I started my ServiceNow career back in 2013 there were mainly three technical roles:

  • System Admin
  • App Developer
  • Implementation Specialist

maybe those roles were enough at the time, however as the platform continues to grow ServiceNow introduced Architect certificate and also we now see a great emphasis on the architect role

so, What does actually ServiceNow Architect suppose to do ?

Continue reading →

Single Responsibility Principle

I am reading great book at the moment titled Clean Architecture A Craftsman’s Guide to Software Structure and Design and I ask myself, is there anything I can apply from this book… i think the answer is yes! As ServiceNow professionals, can we learn anything from Single Responsibility Principle for example? I think yes again.

But first, what is Single Responsibility Principle?

Continue reading →