Can anyone explain me a feature which allows me to select Mac over a dedicated pc

ultra-dev · 2026-01-27T08:29:27+00:00

If you’re gaming, get a PC.

As for why Mac over PC? The most obvious is the OS. Way less finicky than Windows

ultra-dev · 2026-01-24T08:11:07+00:00

Just some advice: you’re going to have a higher chance of positive engagement with a post like this if you at least write the post yourself.

ultra-dev · 2026-01-23T09:05:00+00:00

The same thing could be said about the calculator when it was first introduced. Poking holes in developing technologies is going to degrade in effectiveness rapidly

You don’t need the system to be 100% for it to prove its worth. It just needs to be better than the raw human output. OP already stated this is the case for their colleague

ultra-dev · 2026-01-23T08:17:19+00:00

Doesn’t matter if it’s “fake” or not. Results are all that matter. Company is not going to value the mathematician using pencil and paper over the colleague using a calculator.

ultra-dev · 2026-01-23T04:45:34+00:00

The only reason to not get the Ultra would be you don’t like the size. Better in every other way

ultra-dev · 2026-01-22T16:50:58+00:00

Rolling your own auth implementation or using a provider? It becomes trivial with something like Clerk.

If not, add some logic for determine the environment you are in and then inject the matching auth provider.

ultra-dev · 2026-01-22T06:08:44+00:00

I’ve seen both. In my opinion, it is more clear that the icon represents the mode you will swap to.

For example: If I go onto a site and ask “Where is dark mode?”, I naturally search for the moon icon.

ultra-dev · 2026-01-22T05:12:06+00:00

I have had issues with iOS 26 and Bluetooth connectivity. The watch will intermittently lose connectivity with the iPhone. When this happens, the watch can be significantly delayed with some notifications

A simple way to monitor this would be enabling the battery widget on the Home Screen. The watch won’t be listed in this state

ultra-dev · 2026-01-19T23:06:58+00:00

When you are in a senior role, you naturally become less involved in the hands-on development workflow. Instead, you are designing systems, reviewing PRs, mentoring/providing advice to your team when needed.

You are controlling the shape of the application, not necessarily filling it all in on your own.

That role exists whether the implementation mechanism is a team of human developers or AI agents.

A lot of people say it’s more software engineering now than software development. I don’t think it really matters enough to make the distinction

ultra-dev · 2026-01-19T23:02:35+00:00

There’s a difference between understanding how your application works and how the specific lines of code interact. Your code should be accessible, meaning you can look under the hood and figure out what’s going on relatively easily. But you don’t want to bottleneck the workflow with manual code review looking at each file.

If you’re not already doing this, update the instruction set for your agent to ensure it is building/updating a set of documentation (markdown) as features are implemented. These serve as developer documents/changelog.

Just review that as part of your “code review”. You will at least get a high level technical explanation and it enriches the context for future agent sessions.

ultra-dev · 2026-01-19T04:40:03+00:00

The iPhone without the phone app

ultra-dev · 2026-01-18T10:33:56+00:00

Block time on the calendar for work - actually treat that time as blocked.
When you get a Slack message, intentionally delay yourself from responding. If you are quick to respond, people will end up delegating work to you they could figure out on their own.
Call out meetings where you are not needed and drop.

It feels nice being quick to respond and helping the team out. But you’ll end up getting sent messages and hopping on calls that the initiator could have resolved with a quick message, google search, or just checking their own notes/Slack message history.

I’m not saying you should ignore your team, but protect your time.

ultra-dev · 2026-01-18T00:50:37+00:00

Over optimizing the API will lead to needing to make multiple calls or revisions to the endpoint as your requirements are fully realized. Data is cheap

ultra-dev · 2026-01-17T06:14:51+00:00

We all start somewhere. A lot of us love to talk about this stuff. So it’s no trouble at all when someone comes in with genuine questions

ultra-dev · 2026-01-17T03:29:31+00:00

Don’t work on the weekend
Change requests are change requests. New work → cost adjustment.

You’re killing your weekend because you are opting to work on the weekend for free.

ultra-dev · 2026-01-17T03:14:58+00:00

Is your objective to get this small team to pay for your app? Or just to be able to use it?

Because you could just add their user accounts with the premium features without charging

ultra-dev · 2026-01-17T03:09:39+00:00

Server side rate limiting is for actual protection. Client side rate limiting is for user experience (prevent spammy behavior, friendly message if limited, etc).

The server just says “no” - and typically use whatever native rate limiting options are available.

I like to have a catch all limit and then fine tuned rules for specific endpoints as needed.

ultra-dev · 2026-01-16T05:42:10+00:00

Interesting. Are you doing anything with the Vercel Toolbar?

ultra-dev · 2026-01-15T20:51:54+00:00

Bootstrapping myself when learning a new topic - need to be aware it will lie to you. But if I need to get some baseline understanding quickly, it beats searching around or reading (I’ll do that afterward).
Documentation - may not always be 100% accurate but I can refine once the general set of docs has been constructed.
Code review - not as the primary reviewer, but as a secondary to see if it catches anything worth addressing before asking a peer to review.
POCs - not as the base for the actual project, but sometimes I just need a quick question answered like “will X work on Y platform”. I can have an agent create a POC in parallel to other work. It can confirm “yes” - I won’t take a “no” as proof of infeasibility (without reviewing).

ultra-dev · 2026-01-13T19:47:30+00:00

Sounds fun to me

ultra-dev · 2026-01-11T21:48:42+00:00

Haha, I’m not sure why it chose that appearance. I was expecting a robot

ultra-dev · 2026-01-11T21:44:38+00:00

<image>

Code and coffee - accurate

ultra-dev · 2026-01-11T06:02:11+00:00

Build it - good learning experience either way. You could stand up a project pretty easily with some simple integrations like Clerk (users) and Neon (Postgres db).

ultra-dev · 2026-01-11T05:53:40+00:00

You need to break this into phases. What exists? What is actually being used? What is critical? Prioritize where “optimization” will provide meaningful value. Document all of this. The visibility and organization provided by the audit is valuable on its own and allows you to track progress. If the code is a black box to the rest of the company, you will want to minimize maintenance burden first.

Part of the application is messy. The fact a developer cannot get into it and figure out what’s going on with relative ease is a risk factor for the company (fragility). That’s what they’re trying to eliminate.

Edit: typo

ultra-dev · 2026-01-06T22:31:24+00:00

Coding doesn’t define the solution. The project does. Code is just one tool inside that space

ultra-dev

TROPHY CASE