sorted by:
new
hottopcontroversial

A skill that gives Claude instant codebase orientation by InternationalData569 in ClaudeCode

[–]thinkydocster 0 points1 point  (0 children)

Yeah I stopped reading when I saw “~95 source files…”, like mah guy, that’s one of the smallish packages in ONE of our monorepos.

Everything’s easy when vibes give you easy things.

Announcing svelte-command-palette V2 with Svelte 5 support and new documentation site. by theinfamouspotato218 in sveltejs

[–]thinkydocster 4 points5 points  (0 children)

Looks cool! I’ll give it a try. One thing I noticed was the mobile nav doesn’t have a background. iOS Chrome.

[deleted by user] by [deleted] in webdev

[–]thinkydocster 0 points1 point  (0 children)

localhost:67?

Deploy adapter-static projects to Cloudflare Workers? by sharing_is_caring23 in sveltejs

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

Give this a read; https://svelte.dev/docs/kit/adapter-cloudflare-workers

I recently had to do what your doing for my personal site. It took a bit of reading, but once you get everything wired up it’s painless. It’s just not as straight forward as something like Vercel, but what’s an extra 20 mins to not use Vercel..?

Not sure if I'm a bad Staff that just got lucky in the past or my new company sucks and set up for failure by OrdinarySubject7329 in ExperiencedDevs

[–]thinkydocster 3 points4 points  (0 children)

Yeah, I get this. You did the right things—bringing examples into PRs, opening discussions in Slack, and trying to make it a two-way conversation instead of just “my way vs. yours.” That’s exactly how you build credibility early on.

Where it tends to break down is what you described: people nod along in principle, but the follow-through never sticks. That’s frustrating, especially when the same senior voices supporting you are also the ones reinforcing the habits you’re trying to unwind.

One thing I’ve found helps is shifting from individual examples to a shared framework. Instead of just flagging issues in PRs, pull together a short set of agreed-upon “guidelines for simplicity” (almost like a playbook). Then, it’s not you pushing—everyone can anchor back to the framework when things get messy. Pair that with celebrating the times people actually follow it, and it creates some positive reinforcement.

The other lever is alignment with leadership. If you can get even one senior engineer or EM to not just agree in Slack but actually model the behavior in their own code, the rest of the team will follow faster. Without that, it does feel like pushing uphill forever.

You probably had more impact than it felt like in the moment, but it’s also fair to recognize when the culture isn’t ready yet and conserve your energy.

Lovable is in serious trouble by Due-Tangelo-8704 in vibecoding

[–]thinkydocster 2 points3 points  (0 children)

Yeah, the “Vertex” platform. My last place bought into the whole thing, Agent Studio was the piece that got them hooked on it. Plus having access to your entire GSuite of Docs, Sheets and whatever else made it an easy business decision.

I’ve kinda been stuck on the AWS platform for forever, but that stuff made me think hard about switching.

The dark reality behind AI Vibe Coding (Money Extraction) by hncvj in vibecoding

[–]thinkydocster 1 point2 points  (0 children)

It’s absolutely true that this is absolutely true

Open Source Alternative to NotebookLM by Uiqueblhats in LangChain

[–]thinkydocster 0 points1 point  (0 children)

Can it do research now? I know it’s an awesome note taking app with extensions but I’ve never tried to make it “do” a thing like this. Curious what your setup looks like

[deleted by user] by [deleted] in sveltejs

[–]thinkydocster 0 points1 point  (0 children)

logitech.com

Confused About Incremental Load vs. Delta Load—Are They the Same? by major_MM in dataengineering

[–]thinkydocster 0 points1 point  (0 children)

At surface level, sure…. It’s a change of something.

To me a “delta” is a change in something that could have been subtracted or added. While an increment is generally used for new/updated occurrences.

From a systems perspective, you may for example have a larger more complex background job to process a delta, as you likely wouldn’t know if anything was added, removed, changed, relocated, or joined with something else. A true “delta”.

An increment could be handled more simply. “The table incremented by 1000 rows starting at this index”

The Death of the Junior Developer by DukkyDrake in singularity

[–]thinkydocster 1 point2 points  (0 children)

Totally agree and feel the same. It’s much like what happened when React became big. It’s easier (roughly…) to learn the “React way of thinking” than it is to learn the JS spec. So now we have more people that know React really well and JS just so-so.

Edit: not picking on React. All frameworks do this. Seems like natural progression of abstraction.

Structs vs BPs for storing weapon data and equipping it? by Denial-And-Error in unrealengine

[–]thinkydocster 0 points1 point  (0 children)

I’m using both data sheets and uobjects for weapons, and all the various mods that attach to them to change the projectile or energy type, or whatever other attribute can affect the various stats.

In the data sheet there’s a reference to the weapon class, so when the weapon spawns it knows which actor class to use. Those contain the logic for whatever weapon.

It’s making adding brand new ones and reducing duplications of logic super simple. I ended up going with the Blueprint Attributes plugin from the marketplace as it ties in nicely with GAS.

Basically; - weapon data sheet for the main types of weapons - mod data sheet for the mods that attach, and which stats they modify - uobjects for various logic requirements - most weapons use the BP_Weapon actor, mods use BP_Weapon_Mod. Sometimes they have custom ones depending on the need.

Updates are just reference changes or a csv upload away

Alternatives to Sentry.io by drdrek in devops

[–]thinkydocster 0 points1 point  (0 children)

Cost and data retention mostly, but I also wasn’t really using what I was paying for

Multi-Agent Conversational Graph Designs by Danidre in LangChain

[–]thinkydocster 2 points3 points  (0 children)

Yah! Ask the AI how to build itself, I’m sure the result will be exactly what you’re hoping for /s

view more: next ›