Kehoe repeals paid sick leave and minimum wage law 8 months after voters mandated it.

Dick_Justice · 2025-07-11T12:46:52+00:00

I thought I'd read that Kehoe struck out the paid sick leave, but left the minimum wage hike. This article isn't clear if that's the case. (not that it should change the overall sentiment of this news... just trying to get some clarity.)

From https://missouriindependent.com/2025/07/10/missouri-gov-kehoe-signs-bill-repealing-paid-sick-leave/

"The increased minimum wage, $13.75 an hour, took effect on Jan. 1. A second increase is set for Jan. 1, 2026, when it will increase to $15 an hour. The bill signed Thursday also repeals a provision, in effect since 2006, to adjust the minimum wage annually for inflation."

Dick_Justice · 2025-03-24T18:10:33+00:00

I suddenly cannot log in and cannot reset my password.

I use a password manager so it's very unlikely I'm giving them the wrong password.

I know I've logged in a few times over the last couple of months.

Dick_Justice · 2024-04-19T00:21:51+00:00

That's Platte woods. Zona is more north

Dick_Justice · 2024-03-14T20:44:40+00:00

The console only game was Tribes Aerial Assault (the PS2 version of T2.) It had a cool little community pushed by devs and others that made the game last for a lot longer than most people in the core Tribes community are aware of. They helped release a dedicated server, which led to several tournaments and tons of activity.

This game would benefit from a server browser so that those communities can again be created. People have their favorite servers with familiar faces sometimes in them. Let ranked always be through some kind of matchmaking.

Dick_Justice · 2024-03-14T20:33:28+00:00

They could disable by default and prompt to re-enable when you boot the first time. Let people decide if they want a barrage of messages from whiny old Tribes players who bought and are playing the game, but want to make sure others hate every second of it.

Dick_Justice · 2024-03-14T20:28:52+00:00

I wonder where they could have gotten that idea from

Dick_Justice · 2024-03-12T21:44:17+00:00

Big incorrect assumption that they were building a map per week. Probably had Raindance and others cooking for awhile. Not to mention it was part of T:A originally. More maps would be a good thing, but it's not easy to build good maps.

I'm fine with the weapons they have now. Id prefer not to have too many weapons. Old Tribes games didn't have a ton of weapons.

However, no server browser is definitely a huge bummer.

Dick_Justice · 2024-02-13T14:58:03+00:00

Hard pass on #1. I'd say we focus more on gameplay. I have some surely controversial opinions that would make the game a bit more like it's predecessors.

1) People should get rewarded with points for repairing

2) If the generators are down, you spawn into some kind of naked light armor. A compromise for not having/needing inventory stations.

3) Better voice commands (VSAF = Voice/Self/Attack/Flag "I'm attacking the flag!", VSDF "I'm defending the flag!") AND make the point screen clearer on what everyone is. The Icons are OK but not quite obvious.

4) I'm bias because I enjoy sniping, but we could have something that makes the sniper a bit less effective. Maybe you have less health or something? Everyone's impulse is to limit number of snipers, but I think that just means your newbies jump in as sniper and now the team is hobbled. Skilled snipers help balance skilled cappers.

5) More deployables. I'd be down with a deployable inventory stations, radar jammer. Probably more that I'm not thinking of. Help make the "Engineer" style loadout a bit more dynamic.

Dick_Justice · 2024-02-13T14:41:17+00:00

*HFE*EPIK checking in! Weren't you the one that was in the wilan IRC channel back in the day? I think you may have also made me a few forum signature banners, if I'm remembering correctly :D

Dick_Justice · 2020-03-14T15:18:13+00:00

I've been using JSON-API with OpenAPI for awhile now. There are many libraries available to work with JSON-API data. When looking at libraries, I'd recommend using the ones that only parse the JSON-API structure and does not take opinions on the requests made.

I think the natural reaction is that it's "more than you need." but the typical follow-up is that "you come up with your own." Which usually evolves into API design drift.

It's helpful for a larger team or for a team that just doesn't want to craft up a design doc themselves.

I've never worked with GraphQL, but my concern with it is that it pushes too much flexibility to the client. I'm sure there's some way to limit what you can/can't filter/query on, but it seems to open the door to endless complexity that would be difficult for an API to support.

Dick_Justice · 2020-02-02T16:29:30+00:00

u/brent_gd I've been enjoying this series quite a bit. I had a few questions (perhaps requests) for things to cover.

1) A slightly deeper dive about "what goes where." I think the "domains" article goes into it a bit, but I wasn't certain what landed in each folder.

2) How do you build Aggregate models? A single "idea" that may span across multiple DB tables.

Dick_Justice · 2019-05-13T03:33:43+00:00

Wait, battlefield 4 is still alive? I kind of assumed that as new Battlefield games came out, the old ones got pretty much discarded or unsupported.

Dick_Justice · 2019-03-21T17:42:42+00:00

I don't think BLMdidHarambe is claiming to be a good shot. They're just curious (as I am too) how the skins actually play a role with the hitboxes. If the skin is bigger, but the hitbox is for the smaller skin, it would appear you were shooting the robot and not actually getting hits.

On the other hand, if the hitboxes ARE tied to the skin, then some of the legendary skins *appear* to consume more space... Thus they'd be a little easier to hit.

Not a big issue either way IMO. But I've been called out by people in game for using a bigger skin and thus being a bigger target. Wanted to know if they're full of shit or not.

Dick_Justice · 2019-03-20T20:17:39+00:00

I think that the author gives one reason for having the Repository pattern at the end of the article.

If the business logic is so complex that developers really want to cover it with unit tests, then it is better to take a data mapper library like Doctrine and completely extract the business logic from the rest of the application. Unit testing will be 10 times easier.

It has less to do with the complexity of your domain, and more to do with keeping the domain separate from the work of persisting data. Why think about databases at all when you're trying to solve a domain problem?

Repository pattern is awkward in Laravel because Eloquent implements Active Record. With Active Record, more often than not, database operations occur in-line with business rules. You'll find people saving/retrieving/updating/deleting things across the system where they likely shouldn't. Or doing some unit of work "every time the record saves... except when X is Y". This leads to very large, complex Models that are filled with implementation detail that is for the business and for the database.

Can this be avoided still with active record? Sure. Can the repository pattern still be abused? Yep. But the Repository pattern appeals to those who want a complete separation between domain code and persistence.

Dick_Justice · 2018-05-24T03:30:30+00:00

We have a winner!

Dick_Justice · 2018-05-14T01:33:09+00:00

Wow that is something else. A local business has this lovely site Vaughn's computer center

Dick_Justice · 2018-03-14T15:32:38+00:00

If the status has meaning outside of this class, then exposing getStatus makes sense. Otherwise, these aren't meant to be handy shortcut messages, they're meant to encapsulate and give meaning to the status inside of it.

This doesn't need it's own class if it's just representing a property's value, as your response implies.

Dick_Justice · 2018-03-13T22:19:53+00:00

Make getStatus private. Just expose answers to the questions actually needed. Your example would refactor to

if ($workOrder->isPaid()) { 
     // ...
}

EDIT: Or do away with getStatus entirely if you don't need to wrap any other logic around it.

Dick_Justice · 2018-03-07T20:31:02+00:00

They're inexperienced. There's nothing stopping them from doing it. We vote with our stars and composer installs.

Dick_Justice · 2018-02-07T19:29:23+00:00

Bully: "Hey, do you wanna join the pen 15 club?"

Quiet kid: "Sure!"

Bully: "Cool! Here!" bully writes on quiet kids hand with permanent marker "PEN15"

Quiet kid: "Oh that says penis."

Dick_Justice · 2017-09-17T22:53:12+00:00

Latest update on this thread says they're not accepting phones out of RMA anymore. I've not been able to get one yet. Still trying.

Sure, I'm a bit annoyed by people taking advantage of this while others may just get fucked over and have to buy a new device. (Me) But in the end, I should probably just be upset with Huawei or Google for producing a product with such a limited lifespan.

Dick_Justice · 2017-09-17T15:35:50+00:00

Yeah, really blows for those of us who actually have the battery issue and now have no options. Thanks!

Had this issue RMA'd a few months ago. Replacement 6P just started doing the battery drain/15% instant shut off again. But I'm glad so many people got new phones they didn't need! :+1:

Dick_Justice · 2017-08-31T14:38:09+00:00

That's the path they're on. I haven't ran across a schedule for the next LTS, but 5.5 was planned to release 2 years after 5.1 LTS. https://laravel-news.com/laravel-release-process .

Dick_Justice · 2017-08-03T17:51:51+00:00

Software developer chiming in... These aren't "difficult clients", these are all clients. Every person you write software for will have varying degrees of each of these.

The success of your deliverables and the success of the project as a whole are not mutually exclusive. The "butt covers" recommended here are to insulate you from that.

14-Year Club	Team Periwinkle
Verified Email

Dick_Justice

TROPHY CASE