yurishimo

2,476 カルマ登録 9 年前

Twitter: @daronspence;

mastodon.social/@daron;

meet.hn/city/nl-Weert

Email: daron @ hey

コメント

昨日議論

Actively trying to fight against this now. Crazy huge amount of tech debt with 3 separate rewrites inside one unified monolith repository. Management could only be convinced to let engineering move forward with features on a new platform so now we have periods of code for each rewrite that contain certain features.

With more disciplined engineers we are slowly cleaning it up but it is taking years to realize because management won’t allow work to be stopped on feature development. If we’re lucky, we get two sprints a year to fix things, usually around holidays when half the team is afk anyway so not a huge chunk can be fixed. Then on top of all of that, if you break something when trying to Boy Scout rule improve things, you get chastised and management clamps down more on “scope creep”.

Add in LLMs and now engineering management is convinced that they will solve our problems. Except it can’t really because the project is so spread out and disjointed that it’s impossible to reason about. You’d spend tens of dollars just to have it follow all possible branches of our most critical user flows (and then with hallucinations on top!).

I’m not saying the bots aren’t useful, but they cannot comprehend a disaster zone architecture in anything more than extremely targeted chunks. Without being able to see the entire thing, having it reliably refactor is just not possible without weeks of manual testing or taking a risk and being prepared to rollback on short notice. Writing tests would also take many weeks and if the point is to rearchitect to something sane, a snapshot test is not really going to cut it.

It’s a pickle of a problem for sure… and I’m not sure I will survive at this company long enough to see the end (though I’ve been here years already).

昨日議論

Sounds like you might work on a team with some agency to say no to management.

We have some and sometimes marketing comes back with some extra revenue from a partner if we build out feature X Y or Z for their new product launch. The contracts are signed so engineering has to do it or we’re blamed for lost revenue.

A few of those a year and you eventually end up in a similar situation.

5 日前議論

Some people would argue that this is the best way to use AI as it exists today. Generate a POC and then if that POC makes sense, then rebuild it from scratch by hand. Maybe you can still use AI for a bit of boilerplate generation, but you should write all of the business logic and verify it by hand.

Personally, I'm starting to lean more and more towards this approach.

Though, I have to admit, for a well defined bug ticket, AI can be super useful to knock those out.

11 日前議論

Hetzner seems to be a pretty good example. It wasn't solely because of EU regulation, but once GDPR made it a worthwhile investment to companies to segregate their data, European data centers have been growing steadily.

13 日前議論

Fun fact but Central Market actually operates on the same margins as HEB. Their produce in particular is competitively priced. Where they get you however, is that all of their produce is jumbo sized. So yea, you have a competitive price on the apples per pound, but if you want 6 apples, they are on average going to be more than from HEB or a different supermarket.

Subtle, but it allows them to make some fun marketing claims!

19 日前議論

And that the cause can be addressed by regulation. There's no regulation that will protect from bad actors so designing the system to cater to them in extremely specific ways just creates more red tape for normal people.

Said another way, mandating safer intersections will apply to all motorists and pedestrians equally when they interact with each other at a crossing, but if the bus driver forgets to take their crazy pills that morning and the voices in their head say to run someone over, there's no amount of safety systems or auto-stop that are likely to really prevent harm from being done.

In most Western European nations however, we are fully capable of designing and enforcing travel networks that should rarely produce fatalities when it comes to interactions between cars and pedestrians. The reason many countries don't is a matter of political will.

19 日前議論

Many states have extra markings on the card for citizens vs legal residents. A valid birth certificate would also be enough since the US is one of the only nations to recognize birthright citizenship.

Also worth pointing out that most Americans don't have passports and getting one can take anywhere from 6 weeks to 6 months.

Also, you'd have to be smoking something to assume that the three letter agencies are not going to be combing through Anthropic's customer list and assessing for fraud and foreign bad-actors. If you lie, they'll probably catch you eventually and most people are not stupid enough to lie about their identity to the US government and think they'll get away with it forever.

19 日前議論

I would maybe reframe it as fraud being a natural downstream effect of identity theft. I don't need to steal anyone's identity to forge a check but that's also categorized as fraud.

Identity theft also paints a clearer picture of what is required to remedy the situation. If your details have been pwnd hard enough, you might need to get new government documents entirely in order to protect yourself long term.

If a contractor takes my money to install a pool and then disappears, I don't need to reset my entire financial identity. I think it's worth having a separate idea to describe the situation as a whole and not just the specific vector in which a crime might have been committed.

19 日前議論

Depends on the tool. We (mac people) tend to prefer native toolbars and settings menus, but I would say the days of relying on a "native" textarea or button are now behind us.

The other thing I find most Mac people appreciate is a shared understanding of hotkeys and if your app goes against the norm, one of the first feature requests will be to add configurable hotkey support.

Unfortunately, Apple has dropped the ball with their newest native apps in regards to UX and it will take years for them to go back and improve things. The new OS this fall is aiming to start that process, but it will still be a band-aid in some respect.

25 日前議論

That's how most raytracing is done these days anyway. The game is rendered at a much lower resolution, the raytracing math is applied, and then it is upsampled to the target resolution.

If you set the target resolution to 1080p, not much changes in the render pipeline except the that final upscaling step. To get better quality, the lower resolution is bumped up so there is more data to work with for the upsampling, but the scaling performance can be very hit or miss depending on the game as the engine itself often can play a huge role in rendering performance.

As far as rendering the 1080p image at 4k, yea it works fine, but there will always be little artefacts that remain for those looking for them. 1440p seems to be the sweet spot for gamers today, but 4k is really nice for when you're not gaming as most online video is now made for dual use on televisions.

25 日前議論

Also a thing to consider for some digital audio mixers. Many can broadcast an AP for use with a tablet/pc for app-control. No way in hell I'm connecting my mixer to the internet during a show! The last thing I need is some script kiddy DDoS'ing the mixer and crashing my console.

29 日前議論

That might work until someone else in the org gets curious and checks the git history… I suppose some clever obfuscation might be enough to get around that but then at that point you’re basically writing malware for your own product…

30 日前議論

I think a lot of people here don't seem to understand or appreciate the diversity of systems that "web developers" have to work in.

Some people might say, "Why do you need all that oAuth complexity? Rip it out and use a cookie like God intended."

We, the devs/ICs, don't often get to make those decisions. We're placed into teams working on specific features/apps/tools and we often have to integrate with a myriad of business systems by default.

Yea, I would love to work on a simpler system, but I don't get to make that decision. Especially not when my company has been acquired by unbounded VC cash three times in the past 5 years and now I'm forced to fold in my lovingly crafted baby into the behemoth.

30 日前議論

If I had to guess, they were probably wanting to implement something like animations into the UI. Animating a list of items onload in a staggered format is still basically impossible unless 100% of your users are using Chrome. With a JS animation+component library, this type of animation is pretty much plug-n-play.

When the startup is trying to attract customers and also impress investors, sometimes there is a lot of effort spent on the investors just so they keep putting money into the machine. "See! We have an ultra modern/sleek site so it must be some other variable that is causing customers to churn..."

先月議論

Even if it sucks, there is always the possibility that some software you use finally updates and you dont have a good alternative to replace it. Especially if you consider corporate fleets. Many IT departments are okay to let you lag behind OS updates for a major version, but not 2 or 3. So if I am being forced to upgrade, I’m glad 27 is likely going to fix a lot of stuff anyway.

先月議論

I have been a desktop trackpad user for so long now, I literally don’t want to use a mouse for anything except playing video games. The amount of flexibility offered by a good trackpad just wins most of the time as it is plenty accurate for quickly jumping around on one axis.

With a large enough trackpad, you could even move to a 1:1 type of movement, or add that functionality to a layer for the best of both worlds (like gyro enhanced aiming in games).

先月議論

Do you use a Magic Mouse? It’s really not that bad if your only computer use consists of social media and the occasional budgeting spreadsheet.

And before you mention it, yes the charging cable. In reality, plugging it in for literally 1 minute will get you enough battery to last hours. 5 minutes will get you an entire day. Normal people plug it in and go get a coffee or pee and then it’s fine until they log off for the day. Could it better? Of course, but it’s not so large an issue that they are losing customers on it, so it is what it is.

You’re not the target market for an Apple mouse and that’s okay.

先月議論

I and most of my dev friends didn’t update. The reality is that many of us work in a web browser and an IDE all day writing software for non-Apple platforms. The only incentive I have to update is new and compelling OS features or bugfixes. Since major security patches will likely be backported, that just leaves new features and the reality is that macOS’ only new “feature” worth talking about was Liquid Glass considering their AI offering was also an absolute joke.

Given the other emphasis placed on performance improvements (likely in service to helping to mask the slowness of LLM Siri) I’m really hoping this is a modern Snow Leopard release. I’m looking forward to the Apple nerds digging and offering a compelling narrative about why I should care about updating.

And to add on to that, if this is a bug-fix bonanza release, hopefully we’ll also see a lot of positive movement during the beta period to keep shipping fixes. We’re getting a freaking EQ on AirPods!!!!111!!1! It seems Apple is finally taking some things to heart about listening to their users and I’m 10000% here for it.

先月議論

I think the "fraud" they are likely referring to is working 3 jobs at the same time as a software developer. Do all of the jobs know you have 2 others in the same line of work? If you're a consultant and advertise as such, no big deal imo, but I do think there is something to be said if you can't be honest with all of your employers about what other work is on your plate.

Programming is by definition technical work that requires a significant amount of brain power and focus and if I am an employer (a good one!) I would intuitively expect a certain level of focus from each employee that also entails a certain amount of downtime in order to stay fresh and alert.

This is my attempt at a steel-man of their argument. If your employer(s) is happy with your output and you aren't lying about your availability in order to juggle everything, then there is no harm imo.

先月議論

Huh? Vite is already powered by a huge Rust codebase now that the release of v8.0 is live. They spent years developing their own parser and tooling to make it all possible.