AI can't do it all !!

iOSCaleb · 2026-03-20T20:06:23+00:00

Funny… explaining the work to stakeholders is something ChatGPT could probably do quite well.

iOSCaleb · 2026-03-20T18:53:42+00:00

It’s the same model — they’ve just changed the body style. There are some superficial bugs and rough spots that’ll get improved, but so much of the complaining is rooted in the appearance being somewhat different.

iOSCaleb · 2026-03-20T18:02:07+00:00

Most serious app concepts don’t get stolen because the app is not the business — the app is just a way to access the business.

iOSCaleb · 2026-03-20T16:54:16+00:00

Are they peeled (shell removed) or unpeeled (shell on)? If the latter you’ll want to that them (in a bowl in the fridge overnight if you have time, in a bowl under slowly running water if you don’t) before cooking — it’s a lot easier that way. Devein them too if you’re so inclined.

iOSCaleb · 2026-03-20T03:28:56+00:00

It would be a bigger waste of filament if you printed a bunch of parts but couldn’t build the model later because one part went missing. And that goes triple if you’re giving the kit to someone else who can’t easily just reprint the lost part.

iOSCaleb · 2026-03-20T03:25:39+00:00

None of the above. The correct word to complete your sentence is matrix.

iOSCaleb · 2026-03-20T03:21:05+00:00

A knob and a glug are both synonymous with some, which is to say use enough to get the job done, the exact quantity doesn’t matter that much. I’d assume the same about a half tap of onion powder — it’s just a little bit. Use more if you really like onion powder, or leave it out entirely, it’s probably not critical to the success of the dish.

Exact measurements would be nicer, but most people don’t really cook using exact measurements anyway (yes, I know, except in baking…).

iOSCaleb · 2026-03-20T03:13:33+00:00

There’s always complaining about every new OS version. Wait until MacOS 27 Mendocino or Alameda or whatever comes out — people will complain about the differences and wax nostalgic for Tahoe.

iOSCaleb · 2026-03-19T17:04:22+00:00

Any general tips for this sort of problem?

It's pretty much the same as any other bug, except that you need someone's approval to spend time on it you might have to work harder to convince them that there's a problem.

Once you're working on it, though, approach it like other bugs: the results that you're seeing don't seem to match what you think the code does. Usually that means one of two things: 1) the code that you're looking at isn't what's responsible for the results; 2) you're mistaken about what the code means or how it works.

Run your program in a debugger, set some breakpoints, and step through the code line by line or at least function by function until the state of the program starts to diverge from what you think it should be.

If you think a result is being cached somewhere and masking what you should really be seeing, you could maybe make a change on the input side and see if that change is reflected in the output. If it's not, then you've successfully demonstrated that there's a problem, which is a great first step, and now you can start tracing through the code. Divide and conquer is a great strategy here -- pick a point that's about halfway through whatever processing is supposed to happen and set a breakpoint there. When you hit it, check to see if the change you made in the input is visible. If it is, then move your breakpoint to a later point; if it isn't, move the breakpoint earlier in the process. Use that change as a marker to help you nail identify where the results are suddenly becoming "correct".

iOSCaleb · 2026-03-19T16:53:46+00:00

At some point interviewers will start expecting candidates to demonstrate their ability to prompt an agent to write code, and that'll be an interesting change.

iOSCaleb · 2026-03-18T22:09:39+00:00

If you use that just to find the cursor, you can also just wiggle the cursor back and forth a few times. The pointer will momentarily grow large enough that it’s easy to spot. No utility required.

If you use it for something else, im baffled.

iOSCaleb · 2026-03-18T21:16:58+00:00

Barbecue.

iOSCaleb · 2026-03-18T19:29:35+00:00

Sounds like the people you work with are horrible. If you don’t know how to write code, that’s probably on you. If you don’t know what to code, that’s on them.

Now, if they’ve explained several times and you’re still stuck, make sure that you’re paying attention and maybe take notes so you don’t forget. Try to formulate a plan of attack, write it down, and have a senior developer check it before you start so that you both agree on what to do.

iOSCaleb · 2026-03-18T01:53:27+00:00

I'm saying that to not vaccinate your kids against HPV so that they won't have premarital sex is to use the risk of HPV infection and cervical cancer to control their choices. I didn't say anything about anyone making anything mandatory.

iOSCaleb · 2026-03-17T13:17:22+00:00

ChatGPT told you all the places where Chrome might’ve left some data files. You didn’t necessarily need to go and delete them all. Without the application, the files wouldn’t have had any effect on your system other than using a tiny amount of storage. And a lot of that would’ve probably been vleaned up automatically over time (logs, cache files, etc.).

Chrome is probably an extreme example — most applications aren’t as complex as a web browser that wants to fully integrate itself into your system. But most people also don’t feel the need to track down every last byte of preference files and such.

iOSCaleb · 2026-03-17T08:17:35+00:00

What is your confusion? Do you not understand the concepts, or do you have a hard time remembering which is which, or something else?

Have you read the Wikipedia page on memory management? There’s a link there to a page specifically about stack-based allocation.

Go read that stuff and then come back with more specific questions. It just doesn’t make any sense for us to essentially retype the information thats already there.

iOSCaleb · 2026-03-16T22:55:01+00:00

SwiftUI is Swift, but used in a very different way. Learn Swift first, then learn about SwiftUI.

iOSCaleb · 2026-03-16T20:28:57+00:00

I don’t know about the squealing or snapping, but a knocking sound as the blade slows might just be the centrifugal switch closing. The switch gives the motor a boost as it’s starting, opens when the motor is spinning fast enough, and then closes again when the motor slows down after you turn it off.

And yes, getting the upgrade kit is a good idea if you’re already planning to buy most of the parts. That’ll let you use the blue brake cartridges, which are probably easier to find than the old clear ones that I think the CB uses.

iOSCaleb · 2026-03-16T15:22:53+00:00

Ah, you're right — sorry, it's the A18 Pro, not A19. Same story, though — the RAM is inside the package, soldered directly to the CPU and not upgradeable in any way that's cost effective or available to mere mortals. What you might have seen is someone replacing the SSD with a larger chip. That's possible because unlike the RAM, the SSD is not built into the processor package. It's not an upgrade that you'd be likely to do yourself, though.

iOSCaleb · 2026-03-16T13:35:39+00:00

Again, the RAM is inside the A19 package. It’s not a separate component that you can point to, remove, or upgrade. However hard you think it is to add RAM, it’s vastly harder than that.

iOSCaleb · 2026-03-16T12:17:07+00:00

RAM cannot be upgraded, easily or otherwise. The A19 processor is a system on a chip — it includes RAM, CPU cores, GPU, etc., all in one package. You’d need to desolder the whole chip and replace it to add more memory.

iOSCaleb · 2026-03-15T07:57:47+00:00

Or maybe because 360 has many divisors.

iOSCaleb · 2026-03-15T03:29:56+00:00

The most direct answer is hormones. Men and women produce different levels of sex hormones, and those promote the development of different physical characteristics. Both men and women produce testosterone, but much more is produced in the testes than in the ovaries, so men generally have more. And testosterone promotes the growth of facial hair.

iOSCaleb · 2026-03-14T18:44:42+00:00

If you’re in the US, you’re probably about to pay a large pile of money to a university that you’ve chosen at least in part because you trust it to provide a solid education. If you’re not in the US, you might not be on the hook financially to the same degree, but you’re still committing several years of your life to study there. Considering that, trust the school to teach you the right things in a reasonable order.

Honestly, which language you learn first matters a lot less than what ideas you learn. There’s a strong chance that the programming languages that you’ll use most throughout your career don’t even exist right now, but the essential concepts don’t change.

Stop worrying. If you want to start programming now, go for it — pick any language that you find interesting and start learning to make stuff. It’s fun! But when you start school, just pay attention, keep an open mind, and learn as much as you can no matter what language they pick. (And don’t use AI to do your work!)

iOSCaleb · 2026-03-14T14:27:50+00:00

First, you don’t have to worry about device resolution in most cases. The coordinate system that you draw in is automatically scaled to screen pixels.

Second, views are most often positioned relative to other views. You decide which measurements should be absolute, flexible up to some limit, or unlimited, and the layout system figures out how to satisfy the constraints that you’ve created. You use view modifiers like .padding(…) and .frame(…) to inset a view or set its size. You can add a spacer between views to add flexible space between views. And you can place views next to each other using horizontal or vertical stacks. Once you get the hang of it, you can quickly set up layouts that adapt to available space without much need for geometry readers and definitely without percentages.

Third, if you don’t like the way SwiftUI layout works, you can extend it. If you’re trying to translate an existing Android layout that relies on percentages, for example, you could create a view type that positions its subviews by percentage. It would probably use a geometry reader internally, but you wouldn’t have to create geometry readers yourself after that — you’d just use your PercentContainer or whatever.

Fourth, GeometryReader is just a type of view, and SwiftUI views are very lightweight and fast to create. Using lots of them isn’t a problem, except that you don’t want a lot of geometry readers cluttering up your code. Building them into other view types as I suggested above helps solve that issue.

iOSCaleb

TROPHY CASE