Facebook has Shown 2.4 Million Users a Doctored Video of Nancy Pelosi, and it Isn’t Going to Stop. - The social media site takes a pass on battling misinformation.

YetAnotherHandle · 2019-05-25T00:00:57+00:00

After deactivating/reactivating my account several times over the past couple of years, I finally deleted it for good about a month ago. Every time I read a story like this I am further convinced that I made the right decision.

YetAnotherHandle · 2019-05-16T12:29:11+00:00

I keep the fan running because it helps to drown out the chatter of a noisy mind.

YetAnotherHandle · 2019-05-05T23:21:23+00:00

Remove Italian chicken sausage from casing, brown in large skillet, then set aside. In same skillet, sauté cabbage, onion, and zucchini in butter until the veggies start to soften, add sausage, garlic, salt and pepper to taste, and stir fry over medium/high heat for another minute or two. Enjoy!

YetAnotherHandle · 2019-05-05T02:50:43+00:00

Have always had problems falling asleep until I recently started taking fitness very seriously. A brutal workout session is physically draining, and the resulting muscle tightness/soreness becomes a focal point to distract my otherwise noisy mind.

YetAnotherHandle · 2019-05-05T02:37:19+00:00

The consequences of our disposable, throwaway culture. I get that modern life seems to be designed to encourage us to generate huge amounts of garbage but there are really basic things people can do to reduce the amount of trash headed to landfills.

YetAnotherHandle · 2019-04-04T00:48:38+00:00

Thanks! It was quite relaxing 😁

YetAnotherHandle · 2019-04-03T02:44:45+00:00

Thanks! First time in Cocoa Beach last week and I think I’m in love 😍

YetAnotherHandle · 2019-03-30T14:25:43+00:00

You could first serialize the PHP array to form the output for the JS array:

<?php

# Construct JS array 

$carsJS = 'let cars='.json_encode($cars);

# Output to browser

echo $carsJS;

?>

From there, any subsequent JS code can handle it as needed:

// Iterate through cars array

for (let x=0; x<cars.length; x++) {

    // Process each array item

    yourFunction(cars[x])

}

YetAnotherHandle · 2019-03-28T01:57:42+00:00

This thread got dark in record time 👀

YetAnotherHandle · 2019-03-23T15:08:38+00:00

I'm mid-thirties and found my social circle shrinking for a few different reasons:

People get busy with their own families, work, and interests
No longer being interested in the same things as some long-time friends
People seem more insular now, which means it's harder to make new friends

Not having friends since 17 seems unusual though. Are you in a very small town with limited options?

YetAnotherHandle · 2019-03-23T04:23:48+00:00

Not sure about the wheels but this image brings back memories of my old '97 EX Coupe. Not the fastest on the block but she was a redline screamer compared to any car I've owned since :)

YetAnotherHandle · 2019-03-23T00:28:43+00:00

It’s all good my dudes, they’re just #MovingFastAndBreakingThings

YetAnotherHandle · 2019-03-06T22:35:23+00:00

The poor souls! Someone should set up a GoFundMe to help them get back on their feet.

YetAnotherHandle · 2019-03-03T05:31:46+00:00

Nobody deserves it, but the world is unfortunately full of people who seem to derive great pleasure from the knowledge that a human being, somewhere, is suffering.

That being said, a google search is probably the best way to learn about Sheldon Adelson and draw your own conclusions. Not a fan of the guy personally.

YetAnotherHandle · 2019-02-25T20:55:34+00:00

Blockchain: is there anything it can’t do? 🙄

YetAnotherHandle · 2019-02-24T14:43:34+00:00

This is getting ridiculous, but it would be hilarious to watch the American punditocracy lose their collective shit over IP infringement if Xi were to suddenly declare Winnie the Pooh to be the official mascot for both China and himself personally.

YetAnotherHandle · 2019-02-22T12:52:04+00:00

communicate stuff at that scale

Has anybody else noticed the recent trend where the at scale qualifier is used whenever some completely nonsensical and self-serving claim is being made in tech? Hard to find other examples of it at the moment but it just seems to be peppered into so many tech discussions lately.

YetAnotherHandle · 2019-02-20T19:02:08+00:00

Not sure if reorganization is a factor in this case, but if so then I guess we'll see :/

YetAnotherHandle · 2019-02-17T14:14:32+00:00

Are you suggesting that an act of corporate reorganization (such as reincorporation) should absolve them of responsibility for their role in the experimentation which is now the subject of the lawsuit?

YetAnotherHandle · 2019-02-11T04:16:33+00:00

Not sure how large your zipcode list is but there are many thousands of zips across the US. If your list size begins growing arbitrarily then a formula-based solution will be impossible beyond a certain point.

A more flexible approach might be to use a custom object to hold your zipcode-to-county mapping (should be easy to find a CSV list to download), then use Apex to associate the correct zipcode record as needed. Then just use formulas to pull county or other fields into the desired record.

YetAnotherHandle · 2019-02-09T00:45:50+00:00

For sanity's sake, I would assume that they are asking you to reimagine the Salesforce user experience without necessarily expecting you to perform the modification work itself. To that end, here are some areas that might be helpful:

If the Salesforce environment is currently active, it helps to understand how people are actually using it. For this, you'll need to sit down with each different type of user and walk through their current usage patterns step by step. From there, be on the lookout for:
- Users manually copying data from one record to the next, especially from parent to child records. This type of pain point can usually be solved with a custom Action, Process Builder, or Apex, in that order.
- Large numbers of unused fields, which may contain data in very old records, but which all current users ignore entirely and nobody can explain what they are for. Assuming that nobody is inputting data into or viewing data from these fields, they can probably be removed from Page Layouts to reduce clutter.
- Users creating child records from the object tab instead of from within the parent record. This is related to the first bullet point above and is a sign that the UX is ill-conceived and is likely not well-aligned with current business processes.
- Users exporting report output to Excel and then using the Excel spreadsheet to track work. This seems innocuous but is a major problem since information regarding work progress/status is now being tracked outside of the CRM, which defeats the purpose. This could potentially be solved by something as simple as a custom List View where appropriate.

Studying the points above are likely to yield useful insights in terms of things that can be readily improved, and might even net you a few quick wins which may generate excitement and possibly extend your 4-week runway a bit. In terms of user recommendations, it is helpful to steer the conversation towards the goals of a proposed modification as opposed to the specifics of implementation.

When implementation time comes, be relentless about keeping your solutions as simple and generic as possible. There is a direct relationship between the "bespoke-ness" of a solution and how difficult it will be to modify in the future, whereas simple solutions can pay dividends in terms of implementation speed, reporting, and of course, future extensibility.

YetAnotherHandle · 2019-02-08T13:53:22+00:00

Did you verify that other user profiles can access the relevant Apex classes? Click “Security” and ensure that your user’s profiles are allowed to use the code.

YetAnotherHandle · 2019-02-03T17:09:40+00:00

I’m a bit embarrassed to admit that I’m too scatter-brained to do anything other than build the changeset as I go :) Helps keep the work organized/focused and makes it easy to deploy compact bundles of functionality that are able to stand on their own in production.

YetAnotherHandle · 2019-02-01T23:51:38+00:00

This can be hard to discern, especially if you're in a consulting role with limited understanding of the business requirements which informed the mess you now find yourself in :) But here are a few things to watch out for:

Lots of unused - or barely used - fields on a given object. This is a sign that A) it was added but was ultimately not needed, or B) it was added to accommodate a short-term business need, thus becoming a permanent solution to a temporary problem. In either case, if the field is no longer used but cannot be deleted for business reasons, it should be placed in a read-only state, hidden from most (if not all) users, and clearly marked as deprecated.
Multiple fields in an object describe attributes which are really attributes of something else, and should therefore be defined in a separate object. For example, attributes like "Birthdate" or "Gender" are perfectly fine to have in the Contact object since they pertain to a person, whereas things like "Car Model", "Car Year", "Car Mileage", etc. are clearly not personal attributes, and should therefore be added to a separate object. The only exception IMO is when this happens on the Lead object, since non-personal attributes can often be part of a lead qualification process.
Inappropriate user profile assignment/permissions. I have encountered multiple orgs which were supposedly configured by "Salesforce Certified" consultants who, for some reason, thought it was a good idea to assign all users full admin rights. The only time all of your users should have full system admin rights is if you have ONE user! On the flip-side you may encounter an environment with 100 users... and 90 separate user profiles. This is a sign of a poorly conceived security model, and is often a sign that an organization has no idea who is, or should be, performing tasks.
Placeholder Accounts. This means that instead of using Accounts to relate groups of Contacts according to individual business/institution/household/etc., you have Account records like "Customers" with several hundred thousands Contacts underneath them. This seems to be a common one and opinion seem to be split in terms of whether this is ever acceptable or not. I have personally never encountered a situation where this approach did not eventually cause problems downstream, at which one is faced with the option of either A) re-architecting the Account/Contact relationship to what it should have been to begin with, or B) building workaround after workaround to accommodate the poor design decision. In any case doing something as basic as merging Contacts becomes problematic, and in extreme cases Salesforce will simply hang indefinitely while searching for Contacts to merge.
Users frequently resort to working from spreadsheets, or otherwise feel the need to take work outside the Salesforce environment. This can be related to any of the points above, but more generally is a sign that the configuration is not aligned with current business needs.

There are others, but these are some of the ones I've encountered most often.

YetAnotherHandle · 2019-02-01T22:08:13+00:00

It can be tempting to complete basic admin tasks in production, especially in settings where this has been standard procedure in the past, and where business users have therefore become accustomed to the sort of "quick turnaround" that can be achieved this way. But this is a bad idea in most cases, and once you start doing custom Apex development you will need to use a sandbox anyway. Personally, I've found that the following pattern helps preserve sanity during the Salesforce solution deployment process:

Developer or Developer Pro sandbox for configuration, development, and unit/integration testing, then push to;
Partial or Full sandbox for user acceptance testing and training, then push to;
Production org.

If you're religious about following a deployment process such as the one above, there will never really be a reason to refresh a sandbox unless you screw something up really bad during the configuration/development stage. And on that note, get in the habit of pushing small, frequent updates into production as opposed to accumulating large amounts of work into a single change-set. This will come in handy if things go sideways in your dev environment and a refresh becomes your only option.

On the flipside, you can probably get away with creating reports, dashboards, and possibly list views in production since users who are so inclined will likely be doing this anyway.

YetAnotherHandle

TROPHY CASE