From what I’ve seen people mostly used the Epson scanners like the V600, V700, V850, etc.
They stopped making them early this year. Only the top end model for $1500 still exists and I don’t know if that’s because they still make it or just that there is still stock left at Amazon/etc.
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.
Thanks for the heads up. I’ll definitely keep that in mind. I’m curious though, what other downsides did you run into when using iCloud sync? Would love to learn from your experience.
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.
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.
Unfortunately, they realistically cannot. Basically every major infrastructure project gets loads of local opposition which would require substantial political will. However, the currently elected government is the government that let the rail infrastructure get that bad in the first place
AFAIK to fix reliability no new major infrastructure projects would be required (at least for most of the reliability offenses). They would just need to maintain/modernize existing infrastructure and rolling stock, so all things that aren't really opposable.
To achieve the Deutschlandtakt as noted in the article, yes new infrastructure projects are required, but I think most people would be happy with all the existing service running as well as it has ~15-20 years ago.
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.
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.
reply