Interests:
Mobile Development, Open Source, Remote Work, Hiking, Digital Nomad
---
Mobile Developer in Brooklyn. Primarily native iOS but comfortable working on and learning different parts of the stack. Contact me for remote work opportunities or opportunities near Brooklyn.
Submissions
Researchers Claim to Pinpoint Exact Date When Elon's X Started Boosting Right
A chef in a michelin restaurant, unless he/she is the sole employee (very rare) is likely in charge of a team of line cooks and while they may get some time and place to experiment you better believe it will not be when preparing the chefs carefully curated menu and recipes for paying customers who have been on a reservation waitlist for months. Bob decided to cook the broccoli with a blowtorch and substituted some ingredients in table 9s dinner. There is a fire in the kitchen and the NYT food critic is going into anaphylactic shock but Bob at least feels like an artist so we will let it slide.
the claim we are arguing here is not that “linters never make mistakes” it is that “linters are generally beneficial and avoid mostly useless debates we previously spent an inordinate amount of time on”
Most linters have an escape hatch for exactly this which is usually a one line disable comment
I also never have these conversations at work…because every repo uses a linter and the engineers are mature enough to recognize most of these debates as bikeshedding. Every once in a while someone will suggest turning on or enabling a new custom rule with some justification and there is a brief discussion and it is enabled or not. Outside of work in a consulting gig I didn’t have a linter in the codebase and the owner brought on a new engineer, he wrote if else statements all on one line no matter how long they were and removed spaces everywhere because he thought shorter code was better. He balked hard at any feedback about code style and I was told I couldn’t enforce code style or install a linter. I think you will surprised how much you care if someone with a truly weird style starts putting it in your codebase, I always told myself I didn’t before this. After more dumb waste of time clashes like that I quit the project. Now even personal projects get a linter :).
everything has tradeoffs, on the one hand you are right you have one less dependency, on the other hand the maintenance of said dependency is now on you. many times app store connect has changed some api and fixing our release process was a matter of updating fastlane because the community had already dealt with it, that's on you if you have a bespoke delivery solution.
This is cool but also makes me worried about the tendency with llms for all of us to make bespoke solutions rather than building a better community tool or extending an existing tool to solve the problem. fastlane exists to solve exactly this problem in the mobile space.
Was driving in Lapland with a car like this, snow and ice everywhere on the road except in 2 narrow strips of pavement previous drivers had driven over, naturally it was not always in the exact area of lane that lane assist wanted me and I felt it was actively trying to kill me. Was able to disable but turned back on every time you stopped and started engine and I am forgetful.
You are signing up for another hellscape of unmaintainable slop. Enable package cooldowns and only whitelist internal packages and you are better off than 90%
Jira is fine and devs just grow to hate issue trackers because they hate that part of the job. Watch for another one to come and go when people get sick of linear.
I was a fan of Robinhood's mission of democratizing finance and prioritizing UX for casual traders. They seem to jump on every hype train though, crypto, prediction markets, now agentic trading, whether it is ethical or not or good for their customers or not, and it seems like the distance between "democratizing finance" and "finding new suckers" is closing. Disappointing but not surprising.
Not sure i understand. Sure it doesn’t require it but Apple doesn’t trust you to handle it because you’ll probably drain the battery or spam the user or whatever, that is Apple MO, putting themselves in the middle so they can control the experience.
The single persistent connection is just to receive pushes, there is still some daemon controlled by apple in charged of dispatching to correct app.
yeah this is what author hints at with "Push as a battery problem". Apps are limited by default in what they can do in the background due to this, so most apps are in a suspended state not making network calls when you are not using them. To avoid the app having to keep running this stuff is delegated to OS which tells the app, "hey I have a push for you wake up and handle it!" You can send pushes locally but because of the background limitation it is not practical for unpredictable events like messages coming in.
hey now, they should be grateful they get enough tokens for their appointments with ClaudeMD for their statistically below par data labeling performance, we could reduce the allowance if we keep hearing that kind of talk. We have been very generous with portions at the automatic canteen as well, that energy could be better allocated to the maintenance bots in the server farm.
just this week i pushed back on some requirements in a very detailed product spec I was implementing to speed up time to ship. The pm had no idea what I was talking about because the requirements were invented by an LLM. This is not a bad PM, discipline doesn't scale.
a bit of a roundabout way to answer this, but i think most native devs are okay with a self contained app element using webkit, that is what it is there for and generally stuff like rendering html, markdown, a one off static page, it is just a view from UI perspective. When things get more interactive, have a navigation hierarchy, animations etc are when things start to diverge from native feel and performance and you have gone too far.
Just make it a semi-hidden multistep option like browsers when you visit a site with a bad cert, just annoying to leave what you are doing go to system settings and fiddle.
---
Mobile Developer in Brooklyn. Primarily native iOS but comfortable working on and learning different parts of the stack. Contact me for remote work opportunities or opportunities near Brooklyn.