u/s2labs

Noticing that most modern Salesforce projects now focus heavily on Lightning Web Components, UI customisation, and JavaScript skills.

At the same time, Apex is still the backbone for automations, integrations, and backend logic.

So for someone learning Salesforce in 2026:

• Should they prioritize LWC over Apex?
• Is JavaScript becoming more important than deep Apex knowledge?
• In real projects, what do companies expect more from developers today?

Would love to hear from experienced devs, architects, and even freshers working on current Salesforce projects.

At S2 Labs, we’ve interacted with many learners and professionals in the ServiceNow ecosystem, and one common pattern we see is this:

Most people initially focus too much on certifications and too little on practical implementation.

If we were starting again today, we’d probably:

• Focus more on hands-on projects from day one
• Learn core concepts deeply instead of rushing through modules
• Spend more time understanding real business use cases
• Build a strong foundation in scripting and automation early
• Learn AI + ServiceNow together, since the ecosystem is evolving fast
• Participate more in the community and networking side of ServiceNow

Another big realization - Consistency matters more than speed in this field.

Curious to hear from the community,
If you could restart your ServiceNow journey today, what would you do differently?

When we started working with ServiceNow Flow Designer, We honestly thought it would be super simple, just drag, drop and done.

But after using it in real scenarios, We realized there are a few mistakes almost everyone (including me in the beginning) tends to make.

One of the biggest mistakes is trying to put everything into a single flow. It feels easier at first, but later it becomes really hard to debug or even understand what’s happening. Breaking things into smaller flows or subflows makes life much easier.

Another thing we noticed is people often don’t set proper trigger conditions. So the flow keeps running even when it’s not needed, which can cause unnecessary executions and confusion later.

Testing is another area people usually rush through. A flow might work fine in a normal case, but real-world data is messy empty fields, missing references, unexpected inputs… those things break flows easily if not considered.

Also, overusing “wait for condition” can slow things down more than expected. It looks useful, but if used too much, it can create performance issues.

One more simple but important thing naming. Many flows end up with names like “Test Flow 1” or “New Flow Final”. After a while, nobody knows what they actually do.

We still learning, but these are a few things we wish someone had told me earlier.

Seeing strong demand for both platforms, especially with AI and automation growing fast. Curious to know which platform offers better long-term opportunities, learning curve, salary growth, and work-life balance according to your experience.

Would love to hear honest opinions from people working in either ecosystem.

ServiceNow AI Control Tower is basically a centralized platform to monitor, govern, and manage AI agents across the enterprise. It helps organizations track AI workflows, manage compliance, monitor risks, and even control AI-related costs from a single dashboard.

With companies rapidly adopting AI agents, one major challenge has been visibility and governance. AI Control Tower seems like ServiceNow’s answer to solving that problem by giving IT and compliance teams better control over enterprise AI operations.

It looks promising, especially for organizations planning large-scale AI adoption.

What do you all think about it?

Do you see AI Control Tower becoming important for future ServiceNow implementations?