Viktor Rutberg

When annoyed at something at work: use your built-up frustration as fuel to fix the problem #ragedrivendevelopment

@rampatra_ I actually had the same thing at my jobbyjob. We were waiting for review Monday-Friday last week, and app update was finally reviewd and approved on Friday. I haven't waited that long for years.

My app is waiting to be reviewed for the last 2+ days. It hasn't even been picked up for review yet. App Store reviews are taking so long nowadays. Have you experienced the same?

@sstralberg Yeah, that would make sense, as AI lowers the bar for what it takes to create software. What makes me so torn about this is that people that I look up to praise AI for SWE, but my own experiences don't match those praises at all. It makes me wonder if I'm 'holding it wrong'. :-)

@vrutberg Non-software engineers are more enthusiastic (for good reason) about it. But in the full range of activities, AI seems to be more and more relevant in many of them. We also have barely scratched the surface of AI as an organizational (cowork) strategy rather as just a tool.

I feel incredibly torn on the use of AI in software engineering. Some people claim that they’ve never been this productive, or that they have never shipped this much before, with the help of AI. Yet, when I attempt to use AI in my own work, it’s often times underwhelming.

In some ways I feel like software engineering might change forever because of AI. In other ways, I feel like it’s a hype train. The boring conclusion might just be that AI is simply another tool. It’s not always the right tool, but it sometimes is. Just like a hammer.

It often times results in subpar solutions that I would never allow myself to ship. Is anyone else experiencing this rift in the use of AI for software engineering? Am I using it wrong? Are my standards too high?

Another thing I'm battling is UIBarButtonItems simply not always adapting to the content underneath as they should (e.g. changing the foreground color when scrolling over elements). Is anyone else seeing issues like this?

I'm having an issue with my UITabBarController when building for iOS 26, where the Liquid Glass effect doesn’t look right when the app is launched. However, if the app is backgrounded, and then foregrounded again, it looks good. 🤔 Anyone else encountered something similar?

I filed feedback for this to Apple, FB19755368, but I have yet to hear back from them.

@miguelcabeca Bara bada bastu!

🥵

@maxhenningsson Very impressive! I managed 175 weeks, a little over 3 years, which died out when we had our kid.

5 years. 260 weeks. 47km weekly avg. 5 marathons. 9 half marathons. 0 breaks.

As an… – #iOS26 user I want… – a translucent UI that reflects and refracts its surroundings, delivering a new level of vitality across controls so that… – I can struggle to read

@maxhenningsson är du farsa nu? grattis!

taking the dadbod for a spin

@LeahLundqvist As an icke-snusare: which one is before and which one is after? 🙃

What did they do to you, darling 😣 the branding downgrade here is CRIMINAL

So, um, since Twitter is turning into a burning pile of porn bots, trolls, and just general chaos, I'll probably hang out on Mastodon and Threads a bit more now. I'll probably keep this account active as well, though, but probably a bit less active than before.

Also: I need to read up on @Sendable, nonisolated, etc 🫠

I started fixing some of the few errors that we had. That lead to more errors and warnings, fixing those lead to more errors and warnings. Now, 3 hours later, the compiler is crashing and my project still isn't building.

I enabled strict concurrency checking on my jobby job project, and I sort of didn't expect many errors or warnings, since we don't use a a lot of the modern concurrency stuff (yet). Well... holy macaroni what a rabbit hole this turned out to be.

@danielsaidi Note to self: I should really enable strict concurrency checking on my own projects 🫠

@danielsaidi If you were to replace the mutable var with functions for reading and writing, and protect the value using a lock/actor/whatever, I suppose that would make it thread safe. Not sure what's most ergonomic though?

One problem I often run into when enabling strict concurrency for my various projects, is my use of static properties, e.g. having a static var for a standard style. Then there's this, where EmojiKit has a way to register a global emoji provider. How do I even make this work?

her