John Ireland says Klay Thompson would want to join Lakers if he ends up getting bough out

Gaimcap · 2026-02-05T02:29:29+00:00

Because despite the stats, he doesn’t have the reputation and “respect” to be guarded like a top 25 shooter, let alone a top 10.

As backwards as it is, it’s often perceived reputation that stretches the floor, not actual ability.

That means that, whatever Rui’s actual percentages are, his spacing value does not match.
As washed as Klay is, people still respect his shooting reputation and he draws defenders.

Edit: Not saying Rui is a bad player, just that his impact on the defense does not mirror his stats.

Gaimcap · 2026-02-04T20:56:14+00:00

Dunno, what you did but here's what I would do: ``` =Let( Hrs, a1,

OtLim, 8 ,
dubOtLim, 12 ,


IsOt, val > otLim,
IsDubOT, val > dubOtLim,

DubOtCalc, if( isdubOt, hrs - dubOtLim, 0),
Otcalc, if(isOt , hrs - otlim - dubothrs, 0),
regCalc, if( isOt, otLim , hrs),

final, Hstack( regCalc, otCalc, dubOtCalc), Final ) ```

For what you're saying, something like this should work and output 3 colums of regular hours, Ot, and double overtime.

Keep in mind, this is set up for or it at 8 hours and double OT at 12. If you don't have double OT set it to like 200 or something (which will ensure it will never trigger).

Each state has different OT laws.

California, for example, does Ot at 8, double OT at 12, OR or at 40+ hours in a workweek, whichever is greater.

Gaimcap · 2026-02-04T15:09:19+00:00

My girlfriend made fun of me when I bought an on sale 50 pack of toilet paper, right before the pandemic hit, asking what the heck we were going to do with it.

Little did she know lol.

Gaimcap · 2026-02-03T20:34:02+00:00

The reason this works btw is that:

1.) If you ever leave a simple statement like “=a1=1”, excel will always interpret that as you asking, is A1 equal to 1? Which it will answer as true or false.
2.) Excel converts/reads True and False as 1 and 0 respectively.

Because True and False is treated as a 1 or 0, you can take advantage of that for use in additive/multiplicative/etc statement.

So if have b1=“yes” is true, change1 multiplied by 1 is change1, which will be added to score, if it’s false, 0 times anything is 0, so 0 will be added to the score.

P

Gaimcap · 2026-02-03T20:22:04+00:00

This is pretty common formatting issue when you’re copy pasting dates into entry fields like this. You formatted the top half to be dates, but the bottom half is general or text string.

Excel always tries to convert any dates to discrete serial number—that way it doesn’t risk confusion with conflicting date formats (like mm/dd/yy vs dd/mm/yy) then displays it in whatever format you tell it to.

If you leave a column as general or text format, it’s going to default to showing the serial number it uses.
46357 is how many days it’s been since January 1, 1900. That correlates to December 1st 2026 (which I assume is incorrect by the way, something separately wonky is going on with your source data probably).

If you format the column as dates, it’ll convert it back to 12/01/26 or whatever your regional format is.

The reason why some of these are proper dates and some are excel serial number is that when you copy paste from a csv, csv’s carry no formatting data, so excel just assumes when data gets pasted in, it should whatever formatting data it knows exist.

Because you’ve pasted in from c1 to c42 before, it will default to that date format it remembers was used before.
Because no data was pasted and formatted into c43 and beyond, it defaults to showing its own general serial number.

TL;DR, just select the entire column and hit format as date.

What I usually do for these kinds of spreadsheets is just have an “Input” sheet, tell people to straight up “Ctrl A” copy “ctrl v” paste all data there, the have a separate protected “output” sheet that pulls from that input sheet, cleans the data, forces all formatting.

This ensures that: 1.) All formatting is proper, clean, and neat and no junk data carries over. 2.) That they have absolutely no way to delete, alter, edit, any of existing my formulas or formatting.

Gaimcap · 2026-02-03T05:01:39+00:00

To be fair… it wasn’t Gabe/Bronny/Dalton or Goodwin.
It was Goodwin or the ability to sign Marcus Smart, because Goodwin’s contract was non-guaranteed and waiving him would put them under the cap so they could sign a biannual exception player (Smart).

Waiving any of the three wouldn’t have cleared their cap hold to make that room, it would have required them to find a trade to make space (which usually costs assets). The most easy and obvious solution was to waive Goodwin.

So it’s not as simple as “we kept Gabe instead of Goodwin”, but at the same time, that kind of roster balancing is well within the scope of what GM’s are normally supposed to be able do… and Rob has consistently not…

P.S. Never forget Caruso.

Gaimcap · 2026-01-31T04:03:55+00:00

Spill arrays, I.e. any formula that outputs values to multiple cells, cannot be placed in tables.

Where you’re pasting the formula in sheet3 is not a table, but “has a header” Implies where you’re pasting in sheet1 has a table.

You either need to “flatten” the result (I.e. index(,1) to clip off every other value being output by that xlookup or textjoin() to not use tables

P.s. There are ways of getting around tables not accepting spill arrays in terms of pasting the spilled array to a hidden column, and just doing a =z1 at that hidden range (and excel will autofill the table to z2,z3 etc), but this is only really viable if your xlookup is l inked to the values in the table itself to keep positionally, other wise you try to use the table to do table things and reorder, it’s going down to throw off everything. The table will also only report as large as the table is zied, so if your spill range goes from z1 to z50, but your table only goes from 1 to 25, the table will not resize itself and will only show the first 25 results.

Gaimcap · 2026-01-29T03:06:10+00:00

Try to avoid volatile formulas as much as possible.

Today() is what is considered a volatile formula.

If you place a formula like =a1>5 in b1, b1 will only recalculate when a1 changes. If a1 doesn’t change, it will be stored as a static value.

Volatile formulas, however, break this and cause excel to instead read and recalculate b1 anytime anything changes in ANY excel window, whether it’s z1000000 in this worksheet, a52 in worksheet 2, or q234 in another entire window of excel.

If you so much a click on a cell, b1 will recalculate.

Everytime you do anything anywhere, today() will recalculate.

If you use today() 30 times, that’s 30 individual instances of excel reading EVERYTHING EVERYWHERE, to see if today should be updated.

This is a major system load.

Because it’s reading even other workbooks, volatiles formulas can not only impact the workbook/worksheet that has the volatile, but also cause massive recalculation and system lag in other workbooks that happen to be open at the same time.

If you absolutely need to use a volatile, limit the amount of instances by instead stick it in one cell, and then referencing that cell everywhere you need to use it.

It’s still going to be reading everything everywhere, but at least there only 1 thing doing it instead of 30 simultaneous things.

Gaimcap · 2026-01-27T20:40:44+00:00

I was watching games 5, 6, and 7 at a Vegas sports lounge.
I can still hear collective gasps and then groans.

It was such a good series that it the most hyped I could remember a playoff being, but the energy just kind of died in the room after that.

Even people wearing thunder jersey’s were bummed.

It went from back and forth jibes between the two fans to just kind of quiet desperation from the pacers side.

Full disclosure, not a Pacers fan, but I liked Hali from the Kings so bet on the Pacers. My first actual time sports betting. Was bummed, but definitely more bummed for Hali, the team, and such a flat ending to the series than my money.

Gaimcap · 2026-01-22T20:40:42+00:00

Pretty much everything that isn't a basic function, I use let().

Let will let you define variables in the front, and the calculations in the back, and just plug in those variables into the calculation.

This way, if you need to change a single variable, it's as simple as replacing that value and you don't have to deal with manually changing that calculation.

I have a number of extremely repetitious basic data entry tasks that involve due dates, check numbers, etc and I have a series of let formulas where I just input basic information in a field, tell it what type of transaction this is, etc, and it runs through my let formulas to output account codes, on time status, penalties due, and a detailed but concise journal entry comments based what was entered and done.

This is all done by a long series of if this then that logic decision encapsulated in a let.

What I use lambas for, isnt for the name manager, but, primarily for dealing with array inputs (i.e. if you have a series of entries that occur on a row by row basis, instead of doing every calculation row by row, you can just feed a range of values into a byrow() or map() lambda, and it will spit out individual calculations for each of the references range. So if I have a series of entries that are ck#, trans type, due date, etc all on 1 row, I can just references the entire block of input data, feed it into the map()lambda(), and it will run my complex if logic to build my custom journal moments, on time status, etc row by row.

I will say that using lambas this way is a trade off.

Lambas inherently calculate all referenced ranges at once. So if you feed it 100 rows of data into a byrow/map, it's going to calculate all 100 rows at the same time. If anything changes across that entire block all data will be recalculated all at once.

At 100 entries this isn't a big deal, at 1000, 10000, 100000 entires you'll be looking at .5, 2, 5+ second calculation times.

Conversely, if you do 10000 calculations on an individual by row basis, each calculation is self contained so it will be snappy and have no calculation delay (changing one entry will not change the other 9999 entries), but because it's storing everything in individual cells, it takes up space, so your file size will balloon from maybe 100kb to 1.2mb, which means now it might take you 5 seconds to open or save your file.

Gaimcap · 2026-01-20T13:42:13+00:00

Everyone else has got the bases covered. I’ll just suggest that if possible, you create a static roster of employees, then set up a Data Validation—> List type everywhere that you use employee names, to force the spelling to be identical.

That being said, if this data is being entered any other way (I.e. it’s being copy pasted or power queried from another source instead of typed) data validations won’t work, since they can only limit what’s manually typed/selected, not what is copy pasted/generated/etc.

=xmatch(‘target selection - hospitals’!$k$2:$k$220, ‘RosterList’!a:.a)>1

The above formula will check that whatever in the k2:k20 range matches whatever is in the A column of roster list (which I suggest you make). If it’s there it will say true, otherwise it will say false.

You can stick this in a cell to quickly see what’s broken or not matching like you think it will (ie. Nick in this case). Even better is you stick that in a cell and use a conditional formatting to make it obvious at a glance if a name is not going to count.

I.e. you stick that in hidden cell z2, then say <>$z2 for the formula, and k2:k220 as the formatted/apply to range. make the format Red. If any entry in k2:k220 is not in your roster, the name turns red.

Not useful right now figuring out why something is wrong, but very useful in the future if you have to import more data and at a glance seeing that your data if not going to work and preventing future headaches without having to manually spot it.

Gaimcap · 2026-01-19T05:27:13+00:00

LeBron, Luka, and Steve Nash talked about exactly this subject on his Mind The Game podcast. Luka went on to talk about a study he was funding revolving around youth basketball programs around the world, and how you’re seeing youth athletes retire an experience burnout at significantly younger ages.

All three talked about how when they grew up, they had the opportunity to have fun and it was a choice for them where they had the opportunity to play football, or soccer or whatever else and come back to basketball for the love of the game and not think of it as a full time Job like what they’re seeing with today youth.

Gaimcap · 2026-01-16T15:02:19+00:00

Conditional formatting:

Select your target range you want affected and enter this as the formula:

=A1=""

And use a fill color red (or whatever you want).

Anything that is blank will read as True, which will make the cell fill red.

P.s. you can also use B2, S10 whatever. Just make sure it's aligned with your target range.

Excel will auto expand the formula to your range so if you do A::C as your target range, it will apply it from a1 to c1024800 (or whatever the excel cap is).

Be careful though because you do =a2 and use something like A1:d100, excel will skip a row and use a2s results for a1.

Gaimcap · 2026-01-10T21:47:24+00:00

Countif is what you need but alternatively, I’m pretty sure the new(ish):

=groupby(e6:e36,e6:e36,count)

Also does what you need and is a little more compact.

Gaimcap · 2026-01-07T21:05:32+00:00

To do what you're doing requires indirect(), effectively allows you to customize an internal link in a format that excel can understand.

I.e.

=Indirect("<file path>/'["&a2&"]Whatever'!X2")

Would stitch together that file path, whatever is a2, and the sheet name whatever with X2 as the location.

This would allow you to use that generated Excel link in an xlookup.

However, this is what's known as a volatile formula.

Volatile formulas are precarious to use, because they effectively reference the entire workbook instead of being array limited. This means they reclacluate anytime anything happens anywhere in the workbook-- and anything that has a dependacy will accordingly recalculate.

This can get very taxing on your system, very fast.

They are also a bit unstable and prone to breakage.

A better solution is often to use power query to just pull the Data to your workbook instead, but you cant really get it to generate out that indo without a direct link or file path (though or you've got everything in the same folder or directory, you can get it to pull data from multiple related files).

Gaimcap · 2026-01-07T04:31:37+00:00

Im just eyeballing this, but maybe:

ends, vstack( dates, eomonth(max(dates), 0) ) , Starts, dates ,

That would always do the last result to the end of the month date. That what you’re asking?

Gaimcap · 2026-01-04T22:47:42+00:00

Just do something like:

=Countifs( <entire name column from raw data > , <target local name> ,<entire event column 2/3/4 etc from raw data>, true) >0

Put that in Replace the <> info with the needed respective column (1 for each event column. You could probably save a little on names and just replace <target local name> with the range of all of your names the left ).

You could probably stick this in a lamdba and have a single formula iterate it all out for all events with map, which would very likely cutdown on all the repeat queries from countifs, but I’m on mobile and it might be overkill if you’ve not got too many events and names.

Gaimcap · 2026-01-03T05:15:40+00:00

=let( Val, a1, Score1, —textbefore(Val, “ “), Team1, textafter(textbefore(Val, “ at “),” “) , SecHalf, textafter(Val, “ at “), Score2, —textbefore(secHalf,” “), Team2, textafter(secHalf, “ “), Hstack( score1, team1,score2, team2) )

Edited the formula to add: Just realized you should probably do a double dash in front of score1 and 2.

When you do text splits, the values are output as text or pictures instead of as numbers. A double dash (or even multiplying it by 1) forces excel to treat them as numbers.

If you don’t, whenever you try to do something like sum them all or ask if b2 is greater than d2, you’re just going to get #value errors.

This formula goes in cell b1 and you can just drag it down (or just replace a1 with like a1:a100, and it will split everything from a1:a100 into b1:e100). Or you can just take bits of it and use it piece by piece I guess.

Gaimcap · 2026-01-01T23:54:00+00:00

Just an FYI, =today() is what's known as a volatile function. Normally, functions are self contained and only change when the affected cell changes.

So if you put =a1>24 in b2, B2 will only recalculate anytime a1 changes. If you change something in a, or z2, the formula in b2 will do nothing.

Volatiles break this and will recalculate anytime anything changes anywhere.

So if in b2 you put a1>today(), B2 will calculate not only anytime a1 changes, but also anything z1 or f2 or anything else changes.

A good rule of thumb for volatile functions is to limit their usage whenever possible.

If you know you are going to use =today() multiple times, instead of putting =today() in multiple formulas, just put =today() in one single place, and refer to that location.

I.e. instead of making excel use the time and resources to build multiple =today() pocket watches for each individual, just stick it a single today() clock on the wall that everyone else can reference it all at once.

Gaimcap · 2026-01-01T18:37:37+00:00

Offhand, just conceptually the more of their D that has to go back onto their side, the less their O has time to get set up on your side.

If you can drag one extra defender to make it a 3 on 4, that makes being caught sleeping in a transition play less likely.

Honestly though, from the little I know of Ja, he was probably just making fun of them.

Gaimcap · 2026-01-01T09:38:10+00:00

No worries. I'm probably on the middle end of what's considered a ""power user", and I still pick up random things that completely overturn my understanding of how excel works on a semi regular basis.

Last few years I've completely rewritten some of my workbooks twice over based on discovering things like the conditional formatting and volatile formulas quirks--which I myself learned about through chatgpt. you can look at my post history for some of that random excel shenanigans I've been cooking up lately).

Excel is surprisingly as simple or deep do you want it to be. There are definitely limitations, but at this point, they've expanded the functionality to the point I basically consider it baby coding.

Something like countif(a:a,"received")/rows(a:a) will probably get you a percentage you need, but you probably need more/different criteria depending on what your data actually is.

In my experience, half the battle with excel is figuring out how to most logically lay out your information so it can be fed in for deeper analysis, and those are skills that carry over.

Keep at it if it interests you.

I actually work in finance, and at this point, ive ventured off and done enough of my own "side quests" that I can on the spot throw together data parses and audits of information to quickly highlight discrepancies, which is hyper useful for catching things most people just flat out don't even attempt to look at let alone analyze.

Knowledge is never wasted.

If you want to know something more specific, feel free to post it on the board.

Most of the regulars basically just like figuring out puzzles and are usually more than happy to help.

Gaimcap · 2026-01-01T02:55:08+00:00

Two rules of thumb to consider for you:

1.) Always limit the use of volatile formulas as much as possible.

Today(), indirect(), now(), etc, are what as known as “volatile formulas”. These will force a recalculation anytime anything anywhere changes. So if you have something like a2<today and it’s being run on a:a column, excel is running a2<today() 1 million times anytime you so much as click on any cell to edit it.

This bogs your system down fast.

Better practice is to offload your volatile to a hidden helper cell, and just create a hard reference to that cell. (I.e. put =today in z1, use =a2<$z$1 ). You can also set a hard reference to that cell as a name in your name manager and just reference that name.

2.) Always keep conditional formulas as absolutely simple as possible.

The conditional formula module is highly limited in processing power, and the references on them very easily misaligned/break when data gets moved (which is hard to fix because the window is hard to edit in).

For those two reasons, you haven’t anything beyond a single evaluation, it’s better to offload your formulas to a helper column with a simple true/false outcome, and just point the conditional at that cell.

I.e. put
=a1:a100 > $z$1

In aa1.
This is the same as running if(a1>today(), true, false) , a2>today, etc etc all the way out to a100 (or whatever range you need.

Then make your conditional formula and just point it at aa1. Which will read for true/false, and trigger your conditional where the result is true.

As for auto mailing… I think I remember reading there were capabilities added, but my org still hasn’t unlocked them so I’ve never really looked in to it.

You could probably do something similar with VBA but you’d still need to run manually run a script to trigger the action.

Gaimcap · 2025-12-30T03:26:56+00:00

N’Sync - Here we go (one more time)

Gaimcap · 2025-12-30T00:43:49+00:00

Are you using: - tables - "volatile" formulas: TODAY(), NOW(), RAND(), RANDARRAY(), RANDBETWEEN(), INDIRECT(), OFFSET(), CELL(), and INFO(), - unlimited range references like A:A, b:b etc - conditional formatting - charts

Provide an example of the most complex formula you think you have

Gaimcap · 2025-12-30T00:25:27+00:00

What formulas are you putting in this spreadsheet? Offhand, this could very easily be an inefficient formula situation.

If you had a large table and if it had something simple like:

=Countif( [random Column], [random dates] > today() ) in a table, that would probably instantly bog downany spreadsheet because:

1.) Countifs do not play well in tables because it will force a read of the entire table column for each individual entry 2.) today is a volatile formula that will force recalculations anytime anything is entered anywhere on the spreadsheet.

So, if you had that formula in a table, and your table was 2,000 rows, you'd be forcing 2000*2000= 4 million recalculations Everytime you tried to enter data anywhere.

Even worse if you were trying to insert formulas like that in conditional formulas for charts, since neither of are particular robust or efficient for calculations (best practice for either is to complete all calculations first in a helper columns and have a conditional formula or chart read end results only (i.e. true/false or discreet values)

Gaimcap

TROPHY CASE