DEV Community: Peter Witham

I sat back this week and did no work on my personal projects in favor of hanging out a little more in online communities and it felt great and guilt free.

Peter Witham — Fri, 10 Jul 2026 17:42:29 +0000

Ah the joy of shipping, my new game MooFO is out on the Web thanks to itch.io and now to complete the standalone. Then, on to the next project! Play for free at https://peterwitham.com/moofo

Peter Witham — Thu, 02 Jul 2026 14:41:37 +0000

pwitham.itch.io

The curse of learning and discovery has bitten me this week. I watched some great videos for advice on better Godot game architecture and now my about to ship app feels like it needs reworking to "be better". I'm resisting so far and will ship 1.0 as is.

Peter Witham — Thu, 25 Jun 2026 17:38:11 +0000

Job Finder Tracker iOS Updates

Peter Witham — Thu, 25 Jun 2026 14:00:15 +0000

I recently released a new update to my Job Finder Tracker for iOS app. This release has the most requested feature by users.

Easy Job creation using ShareSheet!

Watch on YouTube

It’s OK, you can stop cheering now. I know this one has been a while coming, it was more complicated than you might think. Read on!

The Problem

Users have long requested a quick and easy way to add jobs to the app without needing to manually enter all the details.

For example, using any Job app or Website like LinkedIn you find a job that interests you.

It can be time-consuming and often error-prone to copy and paste from the source to the application.

The Solution

I wanted to make sure the solution was as robust as I could make it. That meant not only trying to capture the right data, but also making it work in as many locations as possible.

So I set to work creating a system that avoids scraping the data directly where often it will fail as soon as the site or app is updated. Or in the case of LinkedIn, they have a system that actively tries to prevent scraping most of the time.

Once I had a system that works with as many popular job listing sites as I could find, I also wanted a fallback that worked with the remaining sources. A random URL from the Internet for example.

With the source data taken care of, the next question was how to easily get the data into Job Finder Tracker.

Thankfully this was easy to answer on iOS. Use the Share Sheet and also Shortcuts availability to expose a way for seeing the data the user is about to add.

This gives the user a way to edit or append anything they want before adding the job to their list.

As a bonus, the URL field in a listed job contains the original source location should the user want to refer back to it.

The update is live now in the App Store free for existing and new users can purchase and install.

As a developer, I'm always working on the wrong project according to my brain :). I need to timebox my personal projects, which is something I hoped I would never have to do. Side projects are my freedom from organized chaos.

Peter Witham — Tue, 23 Jun 2026 18:27:21 +0000

As I near completion of my latest game. I now have to do the hard part and think about the business model: should it go free, should it be paid, should it be an advertising model? This is always the part I try to avoid for as long as possible.

Peter Witham — Sun, 21 Jun 2026 08:46:28 +0000

The death of future engineering intelligence

Peter Witham — Fri, 01 May 2026 17:35:35 +0000

OK so maybe that is an attention grabber headline, and if it is then great, it should be.

As someone working in technology and responsible for making decisions that affect both consumers and engineering teams, I take my responsibilities seriously.

And that is why I’m concerned about the future of good reliable skilled workers in all industries. But particularly the tech industry.

Warning, this is not a rant against A.I. nor a love letter, it is a reality check for the future

As we have seen if you read any tech news related headlines, videos or podcasts. Engineers are being laid off across the industry. Affecting both seniors and juniors.

Companies are scrambling to adopt A.I. for many reasons including a falsely percieved saving in staff overhead. Think of it as saving a penny today to cost a dollar further down the road.

Not only does this affect peoples lives but it also affects the future skilled work force and project/product deliverables. We are already seeing signs of A.I. built tools taking longer and costing more to maintain and refactor compared to convential development.

There is no question in my mind having used and continuing to use these tools to help me with my work that they are beneficial in the right hands. But when things go wrong it often takes longer to diagnose the problem and fix it. And requires human intervention and understanding, not machines.

As companies reduce the head count of experienced engineers this presents a problem that they have yet to recognise.

If A.I. creates a problem, it does not always know how to solve it. This is where human thinking still wins out, at this time at least.

And if you have no experienced engineers that know the technology,products or systems, how can you expect the problem to be solved? This is a context that goes way beyond well crafted prompts.

Engineers often think outside the box to find solutions or debug a problem, they break the rules to find the problem. Machines only know to follow the rules defined for them.

Even worse, if you allow models to feed themselves on the work they produce then you are slowly building a technical debt of inaccuracy that will eventually destroy it’s self.

We are also seeing companies hire juniors to essentially be button pushers that craft prompts for A.I. to do the real work. On the surface this probably seems like a great idea because it costs less and you can replace people as needed (which is entirely the wrong ethical way to think about this anyway).

This also means juniors will be more expendable than ever, this presents the problem of them improving based on long term experience and learning through failure.

In my view, at least for the forseable future. A.I. tools should be used to continue education and abilities and not viewed as a replacement. I can only hope that sensible argument and discussion wins out over the budget watchers and speed to market company decisions.

Job Finder Tracker for Android

Peter Witham — Thu, 16 Apr 2026 20:01:02 +0000

Update on Android app. It's is almost done!

I am thrilled to announce that Job Finder Tracker for Android is almost finished. I have been polishing up little issues as I find them and the interface feels right.

Here are a few screenshots to get you Android users excited while I work through the Google Play Store process.

I’d love to hear your thoughts over on the PeterWitham.com contact page. If you would like to know when it has been released to the store you can use the contact form to let me know and I’ll send an email when the day arrives.

Not everything needs fancy

Peter Witham — Fri, 03 Oct 2025 14:42:18 +0000

I am wrapping up development and preparing to release my new mobile app SubRadar. The time arrived to put a Web site together.

Now I could have gone two ways

Be the engineer in me and over work the problem with lots of good things that I'll never really need
Keep it simple as a product site and move on

Yep, I chose number 2 this time around. All it needs is a simple HTML + CSS site to show the app and provide a contact form.

This also gave me an opportunity to embrace AI for getting the mundane layout done and then tweak by hand. So that's what I did using Claude Code. Something I've come to appreciate for sanity checking my work when things go wrong.

The end result I think was pleasing and after a couple of days of refining the code and making it look the way I wanted, I now have a product site that just needs some videos worked.

The lesson here is that I needed this done, I have the skills to do it but recognize that my time is better spent focused on getting the app done rather than the tasks I've done a 1000 times before.

Something for us all to think about as we love/hate AI and those tasks we'd rather not repeat over and over.

Take a look, I'm happy with it SubRadar.app

What would you build a Web app with today?

Peter Witham — Tue, 12 Mar 2024 17:38:19 +0000

So, if you were to start a new Web app today that needed the following

Frontend
Backend with DB
User registration
Secure to take payments for the service

What would you use? Yes, I know this is some what open ended and maybe a loaded question. I've only used React in the past few years.

But I want to try and recreate one of my mobile native apps on the Web and I'm a little out of date as I have not built one in a couple of years at least.

I am also considering trying a no-code solution since this feels like a good opportunity to explore them further.

Thanks for advice, suggestions.

The Power of Grooming: Streamlining Your Workflow for Maximum Productivity

Peter Witham — Thu, 09 Nov 2023 15:48:05 +0000

I want to discuss something related to software engineering that can be applied to various topics — project grooming.

Let me give you a few examples.

But hold on, there are no brushes involved.

In software development, when following a process called Scrum, we engage in grooming. Essentially, it involves reviewing all the work that needs to be done.

This approach is much more productive than doing all the preparation right before you start.

New work constantly comes in from different sources, such as finding issues, receiving requests, or implementing new features. The details aren't crucial here.

The idea behind grooming is that, at regular intervals (maybe once a week or so), you sit down with your team (or by yourself) and go through everything to ensure everything is up to date.

Each item should have the latest notes and the correct status. Essentially, you do whatever you can to move things forward or ensure all the necessary information is there.

For example, if you had a meeting and took notes, you add those notes to the item.

The purpose of this practice is that, by doing it regularly, you can pick up any item and start working on it at any time. The thing will have all the latest information and be ready to go.

I believe this approach can be applied to almost anything, and I use it in all my projects.

Some of you might think, "Isn't this overkill for side projects or personal endeavors? It seems like managing the work of the work." But here's the thing: you're already doing it. You might not realize it.

However, more often than not, you're doing it too late. You're doing it when you sit down to start something.

For example, you have 15 minutes to write a blog post. If you spend the first 5 or 10 minutes figuring out what to write about, you'll only have 5 minutes for the actual writing. I hope this example helps you understand the concept.

The same applies to other activities, like photography. If you spend the first 20 minutes of an hour-long session preparing your equipment, formatting cards, and connecting cables, you're not taking pictures; you're just prepping or grooming.

Suppose you do the grooming ahead of time and make it a regular habit (which is quick and easy to do, by the way). In that case, you'll find that when you say, "I'm going to write a blog post," or "I'm going to paint a picture," or "I'm going to take some photographs," or "I'm going to work on some software bugs," you'll be able to sit down, grab an item, and start working on it.

This approach is much more productive than doing all the preparation right before you start.

Plus, if you have to do all the prep work at the beginning, it can be draining and prevent you from engaging in the creative process.

So, please take a moment to think about it. If you have any opinions or suggestions or believe this is either silly, pointless or very beneficial and want to share your experience, I'd love to talk to you about it. Consider that an invitation to come on my Podcasts.

The post The Power of Grooming: Streamlining Your Workflow for Maximum Productivity appeared first on Peter Witham.

Don't forget the leaks

Peter Witham — Thu, 03 Aug 2023 14:56:47 +0000

I had spent the best part of a week on and off trying to fix an issue I was having with SpriteKit, one of the gaming frameworks on the Apple platforms.

This was the last bug between development and shipping the 1.0 release, but it was a big one.

I was getting repeated audio and animations where I should only be seeing and hearing them once. After all, how many times does a player have to die to indicate they dead?…once right?

I had re-written, re-architected the code numerous times and was convinced that I had everything right each time. There are only so many ways to change an image and play a sound after all.

Through out the process I had been live streaming the development at https://compileswift.com/livestream like I always do. And many more talented folks than I in the chatroom had suggested things that we tried with no solution in sight.

Then, someone whom I hold in high regard for SpriteKit said they would be happy to take a look at the whole codebase for me. After much defeat and imposter syndrome, I gave in and handed over the code base.

After a while they got back to me and said “Hey, I think you have a leak and retainer in the game scene”.

Now, I had looked at this, but did not see what they had seen. Maybe due to lack of observation on my part, or maybe code blindness had set in.

But sure enough, they were right. Two lines of code changes later everything started to fit into place and away it went happily just taking down the player once.

So there are two lessons here I want to share.

Always take help when it’s offered
Don’t forget to check beyond the code structure and see if something unexpected or unplanned is happening outside of the logic it’s self.

For now, I am sending the last version to TestFlight and hoping for a 1.0 release in the coming week or two.