6 Figures 6 Certs Random Thoughts Thread

Rawtid

Veteran
Supporter
Joined
Jun 23, 2012
Messages
43,323
Reputation
14,628
Daps
119,430
What we won't do is perform wildcard searches on names to identify data. What was the point of putting in a true/false flag field if you aren't going to use it? I hate when people go around poor data habits instead of fixing what's causing the issue. If the users aren't doing x, train them hoes or put automations in the system to remind them.

If users keep inputting trash data into the system, you're going to die trying to write exceptions AND keep up with exceptions. This is why companies rarely have documentation because they rarely take time to develop a standard process.

If your people are anything like mine, you ain't miss shyt.
We were waiting for someone else. I get it though because they "meet" the hell out of these people.
 

Obreh Winfrey

Truly Brehthtaking
Supporter
Joined
Nov 18, 2016
Messages
20,852
Reputation
25,492
Daps
131,965
What we won't do is perform wildcard searches on names to identify data. What was the point of putting in a true/false flag field if you aren't going to use it? I hate when people go around poor data habits instead of fixing what's causing the issue. If the users aren't doing x, train them hoes or put automations in the system to remind them.

If users keep inputting trash data into the system, you're going to die trying to write exceptions AND keep up with exceptions. This is why companies rarely have documentation because they rarely take time to develop a standard process.


We were waiting for someone else. I get it though because they "meet" the hell out of these people.
shyt, at least 5 minutes of every 30 minute meeting on my calendar is waiting on everyone to join, and half the time it's waiting on the person that is hosting it to join. So then it becomes engrained for shyt to start late, and it turns into a self fulfilling prophecy.
 

null

...
Joined
Nov 12, 2014
Messages
29,691
Reputation
5,129
Daps
46,907
Reppin
UK, DE, GY, DMV
What we won't do is perform wildcard searches on names to identify data. What was the point of putting in a true/false flag field if you aren't going to use it? I hate when people go around poor data habits instead of fixing what's causing the issue. If the users aren't doing x, train them hoes or put automations in the system to remind them.

are you talking about sql?

give them a stored proc that does it (on a per "key" basis).

they can use that for their queries and that will help them identify the incorrectly set flags and it shifts the work (resource usage etc) back to them.

also means you might be able to draw a line under your participation and shine a spotlight on their inaction.

If users keep inputting trash data into the system, you're going to die trying to write exceptions AND keep up with exceptions. This is why companies rarely have documentation because they rarely take time to develop a standard process.


We were waiting for someone else. I get it though because they "meet" the hell out of these people.
 
Last edited:

Rawtid

Veteran
Supporter
Joined
Jun 23, 2012
Messages
43,323
Reputation
14,628
Daps
119,430
are you talking about sql?

give them a stored proc that does it (on a per "key" basis).

they can use that for their queries and that will help them identify the incorrectly set flags and it shifts the work (resource usage etc) back to them.

also means you might be able to draw a line under your participation and shine a spotlight on their inaction.
Not necessarily at the coding part yet, more like defining the data criteria for a certain metric. The issues we're having is defining the criteria behind potential new clients. They have a flag field; True = Potential New Client or False not a client because they didn't convert to an actual client.

The users who input the potential new clients on the front end aren't consistent with using the flags and there doesn't appear to be any automation in place to check/uncheck the flag. Instead, they add "Potential -" to the front of the client name and if they convert, they edit the client name to remove it :heh: And it's not just the word potential, could be any combination, hence the wildcard searches.

My suggestion was to automate the front end to automatically manipulate the flag, so the backend definition is clean; Count when Flag = True is better than Count when Client Name like... IMO it's more efficient to clean up the front end where the users are inputting trash than keep coding for exceptions.
 

null

...
Joined
Nov 12, 2014
Messages
29,691
Reputation
5,129
Daps
46,907
Reppin
UK, DE, GY, DMV
Not necessarily at the coding part yet, more like defining the data criteria for a certain metric. The issues we're having is defining the criteria behind potential new clients. They have a flag field; True = Potential New Client or False not a client because they didn't convert to an actual client.

The users who input the potential new clients on the front end aren't consistent with using the flags and there doesn't appear to be any automation in place to check/uncheck the flag. Instead, they add "Potential -" to the front of the client name and if they convert, they edit the client name to remove it :heh: And it's not just the word potential, could be any combination, hence the wildcard searches.

My suggestion was to automate the front end to automatically manipulate the flag, so the backend definition is clean; Count when Flag = True is better than Count when Client Name like... IMO it's more efficient to clean up the front end where the users are inputting trash than keep coding for exceptions.

sounds ... interessting .. :heh:


1NF normalisation == 1 value per cell .. send them this and tell them to :camby:

 

Secure Da Bag

Veteran
Joined
Dec 20, 2017
Messages
40,951
Reputation
21,193
Daps
128,342
Not necessarily at the coding part yet, more like defining the data criteria for a certain metric. The issues we're having is defining the criteria behind potential new clients. They have a flag field; True = Potential New Client or False not a client because they didn't convert to an actual client.

The users who input the potential new clients on the front end aren't consistent with using the flags and there doesn't appear to be any automation in place to check/uncheck the flag. Instead, they add "Potential -" to the front of the client name and if they convert, they edit the client name to remove it :heh: And it's not just the word potential, could be any combination, hence the wildcard searches.

My suggestion was to automate the front end to automatically manipulate the flag, so the backend definition is clean; Count when Flag = True is better than Count when Client Name like... IMO it's more efficient to clean up the front end where the users are inputting trash than keep coding for exceptions.

You better tell the front-end people to learn what a checkbox or a dropdown is and stop letting these users type in their own statuses. :ufdup:
 

Serious

Veteran
Supporter
Joined
Apr 30, 2012
Messages
80,132
Reputation
14,309
Daps
190,853
Reppin
1st Round Playoff Exits
:wow:


But when this recession legit hits, how long will remote work last? :patrice:
Depends on how an organization is setup and if their roles can be sent overseas.


Certain shyt like government or healthcare won’t be shipped overseas.

And also a lot of organizations made a pivot to clearing up office space, so they’re still saving significantly more, not having people at a physical location.


We may see a casual shift back to hybrid situation but overall remote is here to stay.
 

xoxodede

Superstar
Joined
Aug 6, 2015
Messages
11,065
Reputation
9,240
Daps
51,605
Reppin
Michigan/Atlanta
Anyone here with SAFe certifications?

I have a couple -- and about to do the SAFe 5.1 Program Consultant (SPC) in two weeks.

My big sister has it in addition to damn near everything else.

After I get it I'm thinking about linking up with her to do the Gold SAFe partnership for training for another additional revenue stream.
 
Top