jamil7

They mostly help with centralising UI concerns. I’d imagine your camera app has less of that type of code and more code related to the respective camera APIs, which those frameworks don’t help much with. So I’d say no.

It's cute but are there any actual nerds left in big tech leadership? Of the magnificent seven we basically only have Jensen Huang left as a technical leader and maybe you can count Zuckerberg.

Yes, it's a leadership failure and probably time to go, it only gets worse. In my experience. It's a vicious cycle where, as velocity slows, inexperienced leadership gets more and more panicked and starts frantically rearranging projects, features and people in desperate attempts to fix the problem, obviously exacerbating the communication breakdown and gridlock further. It also builds resentment and can turn pretty toxic as everyone starts just looking out for themselves.

Yeah I think they all shed under heavy load as part of some scaling strategy.

In most trading advice, cutting loses as soon as possible and as emotionlessly as possible is emphasised heavily. It's also physiologically one of the hardest parts for people to do consistently.

I don't shoot 120, only 35mm. But I thought you could get away with a high end flatbed scanner for 120 negatives?

In general it's a bit of a closed box, it's not that easy to work with and to me felt unreliable and difficult to debug. Running migrations can be easily forgotten and this needs to be done in the dashboard as far as I remember. There aren't official APIs to check certain things like if the user has quota, what to do when the quota is full, how to communicate that etc. I think you may be able to check if it's enabled though. Another one is its not cross platform in any meaningful way, I thought this would be fine initially but as the app I worked on developed it was clear a web or Android version would be nice to add without being tied to an Apple account. I ultimately removed it and wrote my own optional sync layer with my own auth and no one seemed to mind. This thread might be useful https://mastodon.social/@marcoarment/109540935902363728

Most of those things can probably be worked around and might not be applicable to your app but for me it went to the bucket of technologies not to touch again.

The developer fee is a business expense for anyone publishing software as an entity on the App Store. This is the same as any other expense someone might require for their profession, it doesn't have anything to do with their financial security.

Just a heads up from someone who's gone down iCloud sync path before. Make sure you're aware of the tradeoffs before relying on it for your app. It has a lot of downsides that aren't immediately obvious due to it relying on the user's iCloud storage quota. Many user's don't understand this and will leave 1 star reviews etc.

Had a coworker paste an error log from a repo I maintain in Slack with an LLM summary of the log, three dot points which were written quite clearly in the log if he’d bothered to read it.

There's no incentive for them to do so, so they won't.

There's a lot to unpack here but to me your comment sort of contradicts itself. You're saying these things are in their infancy and therefore not able to produce code at the standard of a skilled software engineer. But you also seem to have an axe to grind against code review, which is fine but wouldn't that mean code review is even more important? At least right now? Which is kind of the point of the article.

You can do over 100k if you freelance but it's risky to be a freelancer in a lot of ways in Germany. Salaries in Berlin and Munich are approaching 100k or over for leadership roles. The problem is COL in both cities is high and Berlin you basically can't get a flat anymore even if you can pay the rent on it.

(e.g. marketing radium water to cure what ails ya)?

Sounds like something the current US health secretary might actually like.

Yeah, also the CI queues start to get longer towards the end of the EU day as the Americans start their day.

The problem of meeting demand is in industrial use and residential heating, both of which aren’t typically electrified in Germany. The problem has more to do with an active war and an industrial sector built on cheap Russian gas.

I also do this quite a lot but pair it with an automated test to repeatedly trigger the breakpoint with different values and round out the tests and code accordingly.

A good way to partition the complainers into serious and unserious groups is to ask for a written plan

This can be good but I've seen it weaponized before by an incompetent cto to deflect and delay any change. He would ask for written proposals on the most minute details until people just gave up trying to fix anything.

Don’t most of these services have config options to protect against doing this? I haven’t used most of these services but it running up a bill during traffic spikes but not going down seems like it’s working as intended?

xCode with built-in live rebuild preview simulator

You couldn't have picked a slower, more buggy, opaque feature to highlight here. Its useful for UI work when it works properly but I feel like I have to mentally prepare myself everytime I switch the canvas on to avoid throwing the computer out the window.

I'll agree on Xcode Cloud though, integrated CI, signing and TestFlight builds with minimal hassle is very nice.

Not the OP but Monodraw predates SwiftUI by quite a while. On top of that SwiftUI is pretty bad on macOS.

Anytype responds poorly to feedback and bug reports from users, they send LLM slop back for any feedback or bug reports sent to them.

I don't spend anytime post-processing or editing apart from occasional cropping. Film gives me a better baseline for that than digital does, at least for what I want and I just prefer the process. Digital encourages a workflow thats a lot more attached to post and being back at my computer rather than just out taking photos.

I think the UX is good and could imagine it being applied well to a much better research tool.

I recently saw a PM newsletter that was detailing how to encourage and "reward" LLM adoption in teams which also kind of stuck out to me. These are genuinely useful but limited tools that now have to live up to huge promises and valuations so tech leadership is trying to force adoption.

10 years ago, the technical aspects would legitimately be seen as a major, perhaps main obstacle to building a product.

Yeah I think that this was really more the advancement of frameworks, tooling and SaaS software. I see it all the time with non-technical people at work who demo something they built with LLMs and its always Next.js, Supabase and Tailwaind that are actually doing the heavy lifting, with the LLM invoking some commands for them. This all gets attributed to LLMs though since this is often the first exposure to those tools for non-technical people. Most engineers also knew how to scaffold a SaaS with Rails, Django or Next.js, Stripe etc. without writing much code.

I've looked at this a bunch of times, from a pure return perspective, yeah equities usually win. But there's enough benefits to homeownership outside of that lens that I think either side can make a pretty compelling argument (I say this as someone who rents). It also highly depends on which market we're talking about.

The article loses impact due to the way the author keeps self-conciously mentioning how the "PHP haters" are wrong instead of just explaining the possible usecase for PHP better.

I've never really used it but it would have been somewhat useful to know why anyone would choose this language for a greenfield project in 2025, given the choices available. The reasons given are pretty unconvincing to me.

What do you mean by access? APIs to program against or fully open sourcing the rendering engine? Because you can mix SwiftUI with a few different rendering frameworks at varying abstraction levels that it itself renders to (AppKit, UIKit, Core Graphics, Metal etc.)

In every public-healthcare country, this happens.

Outside of Canada and the UK this isn't true.

Because incentives are stacked against delivering to the patient and for increasing spendings.

Germany, The Netherlands and Japan all have regulated competition models.

It’s the tragedy of the commons.

Public healthcare isn't a free for all, its regulated, actively managed and budgeted.