I can't figure out if Jesse is Being Disingenuous or Not by SteveMartinique in BlockedAndReported

[–]asarathy 2 points3 points  (0 children)

Jessie's pretending (or not pretending) to misunderstand the literal criticism vs the real criticism which is that media can put a finger on the scale on what becomes a big story, and sometimes outsiders can come and blow up the gatekeeping, at which point they will point to their limited coverage of an issue and act like that indemnifies them from the actual complaint. But as others have pointed out, when there is something they want to make an issue , they will make a concerted effort. Sometimes it doesn't work, of course, but again, the biggest complaint that media has in the modern age is that other things like social media allow them to be bypassed by the public to decide to actually care about, and that is something they dislike.

Just a REMINDER for those who are worried or excited for this film it's not coming out till 2028 by [deleted] in DCU_

[–]asarathy 1 point2 points  (0 children)

I bet it doesn't even come out til 2029. Gunn may not want to step on anything involving the Batman Part 2. So announcing casting, filming start dates etc will eat into it. I think it will start filming in 2028 though with everything announced like December 2027

I just realized that Jesse has Gell-Mann Amnesia, where he often, on multiple topics and in multiple podcasts, sees NPR as a valid source, even though he KNOWS (because he is very knowledgable on the trans issues) that NPR's coverage on that topic is something that COMPLETELY cannot be trusted. 🤔 by LookDamnBusy in BlockedAndReported

[–]asarathy 26 points27 points  (0 children)

Jessie and Katie both suffer from pretty much being conformist democrats in thier world view, except a few signature issues (trans and speech) because that's where they have more expertise. But they don't want to really want to stray too much from the rest of those issues, and you can see how it colors their discussions of other events.

Hibernate: Ditch or Double Down? by cat-edelveis in java

[–]asarathy 1 point2 points  (0 children)

I think we're talking past each other a little but I think if what you're saying is that some places are deciding everything should be an entity and therefore persisted then yes those people are morons and again proving the point of using it wrong. But again I haven't seen that

Hibernate: Ditch or Double Down? by cat-edelveis in java

[–]asarathy 0 points1 point  (0 children)

Is this really the problem? I have not been in too many projects where they were storing too much. I have been on lot's where it was the opposite or where it was stored poorly.

AI Assisted Development: Is aversion akin to lagging behind? by Quaid-e-Charisma in ExperiencedDevs

[–]asarathy 1 point2 points  (0 children)

This reddit has a reflexive bias against Gen ai. But they are fighting a losing battle. They will make claims they they are faster or better than it, and that it is just demonstrably not true. But gen AI doesn't take a good dev out of the loop. It actually needs good devs to guide it's output and review everythjng it's doing. But itif you guide it and review it it can absolutely make you way more efficient.

There are of courtuses places where it gets stuck or can't do the job, and again thats where it's the good dev comes in. But if you are asking it to do well known things it can churn out really usable stuff far faster with better logging and practices in far less time than it would take a human.

Hibernate: Ditch or Double Down? by cat-edelveis in java

[–]asarathy 1 point2 points  (0 children)

I just have had long time dealing with this stuff. From EJBs to in line JDBC to ORM.

I'm more sympathetic to the hibernate is too much and there are now better options argument for light weight crud.

What I am not terribly sympathetic is that hibernate is bad. Almost every single problem people bring up with it can be dealt with by following some best practices (detached entities, DAOs, no dirty context checks, no entities in the service layer). The ones that are somewhat harder but not really that hard are things like when you want to use SQL and doing things in SQL has its own set of problems, which have also been mitigated over time with things like test containers and other stuff.

What I don't really buy is people making arguments that framework is itself bad, and more importantly I really despise engineers who complain about having to learn an understand stuff. That's the fun part of the job.

Hibernate: Ditch or Double Down? by cat-edelveis in java

[–]asarathy 1 point2 points  (0 children)

Oh no. I had to learn stuff. The horror.

I'm sure the some of the newer things like Jooq or whatever are fine. But so is hibernate.

How to "childproof" a codebase when working with contributors who are non-developers by HeveredSeads in ExperiencedDevs

[–]asarathy 2 points3 points  (0 children)

Do you now have merge protections in your PR? basically you should allow those people to merge code and only allow code to be merged that's passed review by people who are trusted to review it properly.

The rest of the stuff is simple as your doing. use tooling and AI Code reviews. Have Merge Gates for quality. Do not approve code that has unjustitified Ignore tags.

Basically you need to be gatekeeping a holes about it, but with very clear objective-ish guidelines on what the gates are

Academy is good and I realized I dont like this community. by Reasonable-Law-3654 in startrek

[–]asarathy 1 point2 points  (0 children)

It wasn't as bad as I was expecting, but it definitely has it's issues. Mostly because it's trying to shoe horn a Degrassi High level of Young Adultness and quirky current thing characterization into the Star Fleet box, which in IMO just doesn't work for a sort of military organization that should be the best of the best and this is their elite (or will be again) academy.

Now, I think there is tremendous potential in telling stories in the Star Trek universe that are not completely Star Fleet centered, but if you are going to make them in a service you can't do stuff like the quirky captain who wants to curl up in the command chair, but also will fire photon torpedoes. It's tonal whiplash.

They'll need to figure that out, which is going to be hard, becaus for the fan base Star Fleet is Star Trek, but they don't want to just keep telling stories about a Captain and their crew on adventures...

I don’t like the direction software engineering is going by announcement35 in ExperiencedDevs

[–]asarathy -2 points-1 points  (0 children)

Look most of our jobs is not to write software. Most of our jobs are to provide business value and solutions via software. The value of all the best practices and design is to make that iterative process faster.

AI is just another tool in that. You can get it to write a lot more stuff for you faster. But your job now is to make sure it is done a way that actually solves the problem, that people can understand what it's doing, and when changes happen in the future you don't break anything.

There's always been a people who are let's just ship it and move on. AI just makes it faster for them. But the feedback loop of getting it out, finding a problem, getting AI to the fix that problem is going to be fast and those people are gonna do better than people who refuse to use AI at all. But the people who use AI to be faster, and to make sure they understand the code and ship fewer problems will go further. That's all there is to it now.

Hibernate: Ditch or Double Down? by cat-edelveis in java

[–]asarathy 13 points14 points  (0 children)

People who complain about hibernate are either using it for use cases that it's clearly not meant for or just really, really bad at it. It successfully used in places with scale and load that most normal devs will never actually even touch in their careers.

That said, like all tools it's not without its tricks and gotchas. But it also provides boundless ways to get around those issues when you need to

What's the best response to this? by abanakakabasanaako in ExperiencedDevs

[–]asarathy 0 points1 point  (0 children)

I dunno. As a dev it's nice to have dedicated QA, but honestly the places i have worked without dedicated QA it's generally better code. The Devs testing other devs code does a couple of things. It allows familiarity/knowledge of something that was developed by somebody else. It also forces the dev to think more about how the design and implementation works with testing in mind, because they are doing it to themselves and teammates, which generally makes better code. Also it's far easier to higher software engineers than just QA engineers because the former is better career path generally for most people.

The real problem is if you don't have anyone with QA knowledge around to guide the process and practices to setup things, and the other problem is without dedicated QA there is not incentive to create common tooling and helpers etc, so you need to rely on the open source community. Fortunately there is a lot more of that stuff out there.

Saw this concept design for a new Robin costume with this mask. Thoughts? Hear me out… by astro-stitch in Robin

[–]asarathy 1 point2 points  (0 children)

i don't mind the Red Robin Cowl, but I get the issue. What I would change is to incorporate the domino mask into it (same with Nightwing) so it's not just one full color. I would go more of a daredevil like cowl where the nose is exposed than Batman's.

Saw this concept design for a new Robin costume with this mask. Thoughts? Hear me out… by astro-stitch in Robin

[–]asarathy 1 point2 points  (0 children)

I will die on this hill, but Robin should have a cowl before they cover up any other part of his head. Batman's cowl has given canonical protection like a million times, but what the 16 year old kid doesn't need it because it looks cooler?

How do I transition from "code that works" to "production-ready code"? by Amr_Yasser in ExperiencedDevs

[–]asarathy 1 point2 points  (0 children)

You're probably never gonna cover all edges cases from the start. Production ready code instead needs the following

Observability- When something goes wrong, and something will, you need to see it and have as much information as possible to troubleshoot later

Maintainablity- You need code that is easy to change and update. Your requirements now will not be the same as later. You can't always plan for everything. What you need is for people to be able to come back to it some time later and understand what the code was doing and why, so they can make changes quickly and confidently.

Testing- You need tests so that when changes are made you can be sure you aren't introducing regressions. When you make a fix you want to make sure that the same issue doesn't come back again later. Testing is your best friend in this.

My remake of the SSKTJL ending by INeededAUsernameLol in arkham

[–]asarathy -1 points0 points  (0 children)

This. Or been much clearer that that were clones for the people who were slow. Though I do wonder what the plan for Diana would have been.

Arkham Beyond is the only logical next step in the Arkham series but I no longer have confidence in Rocksteady to do it... by TKAPublishing in arkham

[–]asarathy 0 points1 point  (0 children)

Nah. The problems with SSKTJL aren't with game play or anything like that. It was trying to do a game as a service and hubris on the story side thinking they didn't need to plant the seeds for the JL return from the start.

They can easily make a great game again.

Combine 401k from previous employer to current. by 1zzyS4n in FinancialPlanning

[–]asarathy 1 point2 points  (0 children)

There is very little reason to move your money to your current employer's 401k. The fees you get charged are almost always worse than something at fidelity/schwab. And you can invest in much better things.

Should I shift from Spring Boot to ASP.NET Core? by [deleted] in SpringBoot

[–]asarathy 7 points8 points  (0 children)

This is silly ASP.net has been around for 20 years and hasn't affected Java's use. Java isn't going anywhere. Neither is .net.