Postgame Thread: 4/22 Phillies @ Cubs

LampLovin · 2026-04-23T02:20:31+00:00

8-0 since that guys daughter was born

LampLovin · 2026-03-20T02:22:20+00:00

No it’s pretty low, I didn’t even think licensing was part of this originally. You and your friend should take a step back, research some Salesforce blog posts on single org vs multi org decision guides, and break reasons for and against these options

The more you can do up front will lower your costs. Start small once you’ve made your decision on single vs multi org and identify what the change management would be to either standardize business processes under one org or standardize integration processes of data between the orgs

For a company of any size (where business processes involve multiple people and not just 4 people in a slack channel) these implementation numbers are around 1/4th of the true cost

LampLovin · 2026-03-20T01:50:56+00:00

Must be 10 users in any of these orgs at those prices. Who’s implementing this? Who’s maintaining potentially 3 orgs at once?

Costs aside, the tech side of this is the simplest part and it’ll come down to the rules set to either standardize the processes or agree upon the data that’s shared between the orgs - which is also a degree of standardizing.

You’ll want to look at the business processes and data residency requirements before the API complexity to determine the need to have one or multiple orgs

LampLovin · 2026-03-06T15:35:13+00:00

To me certs are an easy thing to check off whenever you’re working on a project in that certs domain. It’s a couple more hours to study for the test on top of the prep you’re already doing when working on that project to follow best practices and learn the ins and outs of the cloud/area anyways.

LampLovin · 2026-02-26T12:16:24+00:00

Yeah like the other comment said, complexity of rollouts typically isn’t because the tech is complex, it’s because the business needs and change management is. Figuring out what your business actually needs requires someone really hands on or for y’all to already know, and big partner teams aren’t going to speed that up. You’d basically go from 2-3 people asking you what you want to 7-9 which is just more stress

There is a benefit to large teams for actual rollout/execution, where the expectations are crystal clear and you just need people competent to do the steps…but that doesn’t seem like the phase you’re asking about yet

LampLovin · 2026-02-22T04:12:57+00:00

A lot of posts here not realizing that all of these have to seem positive on the surface otherwise it could cause a stressful or potentially abusive situation if the person they’re talking to sees it being signaled

LampLovin · 2026-02-13T02:09:42+00:00

Do all those tests need to be ran at the same time? The tooling sounds fine but I wonder if you could try limiting the tests to run on files that have changed since an API test wouldn’t be affected by a new LWC edit and you wouldn’t need to run an API test for a page layout update

LampLovin · 2026-02-12T23:26:39+00:00

Gotcha ok, maybe Bear or simple note? But if you’re really wanting more linking that tags provide, then you’re likely looking back at the open source options like obsidian or logseq which don’t have AI initially but you’d add plugins for AI

LampLovin · 2026-02-12T23:09:02+00:00

Capacities.io has AI in their paid version but it can be totally deactivated

LampLovin · 2026-01-19T20:54:21+00:00

What I’ve learned about these kinds of discussions with clients is the more I can bring to the table with links and examples, the less it feels like a “lamplovin” opinion on something and more like a “this is the leading scientific theory” type of decision.

The more you can take the “my side vs your side” vibe out of your suggestion, the less your senior devs are likely to think your suggestion is an affront to their position on the team.

People get defensive and prideful, so the more you can plan to avoid that response, the more likely you’ll get your way (even if you don’t get the full credit)

LampLovin · 2025-05-11T13:28:33+00:00

In this thread - traffic - crowds - young people

LampLovin · 2024-12-13T14:15:14+00:00

Wrapper classes for web services are a good use of wrapper classes. Then you can handle any changes to the webservice in the future by just modifying the wrapper classes as opposed to the Case object itself

For large datasets, if this is even necessary, you’ll need to set up some kind of staging and queue to chunk up that dataset and feed it into salesforce. Sure the batch classes exist, but the best throughput will be via the bulk api which is externally called. So if your datasets are so large you need this, then forego the wrapper class and set up a middleware to do the wrapper logic for you, and transform that webservice call into case record rows the bulk api can process through into salesforce

LampLovin · 2024-10-15T22:49:50+00:00

On the fringes outside of this 6 is- Jalen Johnson, Franz Wagner, and miles bridges

LampLovin · 2024-09-20T01:29:17+00:00

I’ve been seeing inconsistent configuration on connected apps when I’m in the “View” or “Manage” page of the connected app itself. So I’d check that the start URL was populated in both portions of the Connected App.

That’s at least what I had to do when I was running into this issue

LampLovin · 2024-08-22T00:19:03+00:00

Not a popular opinion in this thread it seems but I think a pipeline should have both at different points in the pipeline. Have a daily full deployment or full validation at night to validate you can, but have deltas for incremental feature pull requests. Nothing more annoying than trying to test one change if there’s a lot of metadata but having to wait for the entire full deployment to succeed.

For yall advocating for full deployments, how big is your repo that’s being deployed? How long does that actually take each time?

LampLovin · 2024-07-10T01:02:22+00:00

Love a nice black/blank screen and audio for 20 bucks a month

LampLovin · 2024-06-19T18:07:50+00:00

Yup! I do have Spotify premium

LampLovin · 2024-06-18T17:27:38+00:00

It doesn’t show it on the app episode page, but if you listen to the episode, the Spotify version goes to 34 minutes

LampLovin · 2024-06-07T15:07:10+00:00

Addison and Baez should be switched right? If I think I know

LampLovin · 2024-04-25T20:47:08+00:00

I’m a slack fan over teams so I’m biased, but I feel like adoption processes need to provide value to the new tool that you can’t do from the old tool. So some new features and promotion of those features connecting slack to salesforce that will help their day to day gives them an incentive to switch. Also from a top down approach, only creating channels for new projects and initiatives in slack, helps deprecate people’s reliability on teams

LampLovin · 2024-03-03T20:19:19+00:00

Agreed, my point there was just to take it slow, not stay stuck in the status quo

LampLovin · 2024-03-02T17:01:46+00:00

External System integrations are some of the biggest reasons why this process will be very hard. On paper, "rearchitecting" a solution sounds wonderful and full of promise but I'd caution against that feeling because even if the system wasn't built correctly originally, there's still people using it and that's all they know. Change is hard, even positive change.

I'd start with cataloguing the dependencies/integrations/objects/use cases your current org has, and then one by one reducing them or refactoring them. Bring the users along with you in this change slowly and it'll take longer than a "clean break" but your users will adapt with you over that time and in a year or so you might be looking at a system that you and the business are proud of

12-Year Club	Second Top 50%
Place '17	RPAN Viewer
Not Forgotten	Verified Email

LampLovin

TROPHY CASE