HNHacker News
TopNewBestAskShowJobs

allenu

3,509 karma · joined April 15, 2013

I'm an indie dev making apps for Mac and iOS: https://www.ussherpress.com

My latest app is Understory, a Mac app for students and writers to research, outline, and write – https://understory.ussherpress.com/

[ my public key: https://keybase.io/allenu; my proof: https://keybase.io/allenu/sigs/9lNtoSQ24I0rd8_9OIJb6D9k8F_jqdLfVvZfvN-N2R4 ]

meet.hn/city/us-Seattle

Interests: Entrepreneurship, Mobile Development, Programming, UI/UX Design

---

submissionscomments
allenu··on Apple accidentally left Claude.md files Apple Support app
I can see it happening. It's very easy to drag and drop a file into an Xcode project and when the dialog pops up asking if you want it to be added to the target app bundle you just hit OK, not realizing what you just did. I've done it before with a document file but caught it before I shipped by inspecting the app bundle output.
allenu··on Unfolder for Mac – A 3D model unfolding tool for creating papercraft
I like the clean design of the landing page. I downloaded it and started the app and it needs an OBJ file to even do anything, so I wasn't able to play with it at all.

It would be cool if it included sample OBJ files to entice me to find my own later. Otherwise I feel like I just hit a wall immediately in the app will probably not try it again.

allenu··on Škoda DuoBell: A bicycle bell that penetrates noise-cancelling headphones
I'm in total agreement regarding some designs that seem obvious later but really took several iterations to reach. There's definitely hindsight bias when a design works so well that it feels obvious.

My point was more that I've seen product demos where parts of a product were presented as having been pored over painstakingly when in reality it was decided on day one that it would work that way. However, because it's a prominent feature, it feels cheap to show the reality, so I get that for demos there's a bit of storytelling that goes into it so the audience feels like it was a revelation.

For UX that I've designed myself, I have definitely found that a lot of the great ones required a ton of iteration and almost "courage" to go against my initial bright ideas and look at things from a different perspective. It often required taking away elements that I thought were absolutely required at first but later realized made more sense to go without. If someone were to look at the final result, they would definitely think "Well, obviously that's how it should work." But more likely they'd have go through a similar journey that I did to come up with it if they hadn't seen the solution.

In a way it's like finding out how a magic trick worked. It's only obvious in retrospect.

allenu··on Ask HN: Any interesting niche hobbies?
Sounds like a really cool idea. How do you organize the meetup and promote it to people if it ends up being random people? Do you set it up on meetup.com and have a theme at the minimum?

I've been to a lot of meetups and it's definitely hit or miss and obviously depends on the sociability of the people that show up. The better ones I've attended are generally ones where people aren't trying to network for work purposes and are there literally to just socialize. The networking ones I find very dull as it's people just talking shop and career and if you've nothing to offer them on the career front, they move on quickly.

allenu··on Škoda DuoBell: A bicycle bell that penetrates noise-cancelling headphones
I love these types of videos because they create this fiction of how design happens, where people sit around a table with drawings and or come up with beautiful mock-ups (the motion sickness glasses is a good example). Often, a lot of design decisions are super obvious and don't require a lot of sweat and collaboration to come up with, but in videos they're made to appear very difficult as it presents better. And other things are super messy, but you're not going to show that as it's hard to communicate.
allenu··on Revision Demoparty 2026: Razor1911 [video]
Copy-pasting is a clever way to do it!

I used to use TheDraw for doing ANSI art, but I also ended up making my own ANSI drawing tool back then. It's stupid to think of now, but one reason I made it was because I had a monochrome monitor, so I couldn't "see" color. I wanted a feature where I could put the cursor over a character and it would tell me the color there when I was drawing so I could still use color in the work.

I wasn't prolific, but did do a handful of ANSI art pieces for local BBS SysOps who liked them well enough. Only later on I realized when I got an actual color monitor that I had a few color mistakes in them and they never told me. lol

allenu··on Revision Demoparty 2026: Razor1911 [video]
Beautiful. Masterfully done. I love all the BBS-era aesthetics and callouts. I hadn't seen FILE_ID.DIZ art in forever.
allenu··on Turning a MacBook into a touchscreen with $1 of hardware (2018)
This project brings back memories. I worked somewhere over 20 years ago where we were working on something just like this (touch displays using cameras). The biggest challenge was definitely the lighting conditions as you mentioned. We tried to rely on natural light but it was too unreliable. Darker skin tones were harder to pick up, and then you had issues with random reflections, light and shadow being cast on the screen, etc., which would make the system detect spurious fingers and touches.

We also had algorithms to detect finger shape to detect location of the pointer and when you were touching the screen. I saw way too many videos of fingers touching screens back then, so it's funny to see similar video clips here.

allenu··on Some things just take time
> But if you are running in the wrong direction, speed is of very little value.

I think of it differently. Speed is great because it means you can change direction very easily, and being wrong isn't as costly. As long as you're tracking where you're going, if you end up in the wrong place, but you got there quickly and noticed it, you can quickly move in a different direction to get to the right place.

Sometimes we take time mostly because it's expensive to be wrong. If being wrong doesn't cost anything, going fast and being wrong a lot may actually be better as it lets you explore lots of options. For this strategy to work, however, you need good judgment to recognize when you've reached a wrong position.

allenu··on LotusNotes
It must be a nod to Freud (i.e. id, ego, and super ego)
allenu·
Watering plants is also super easy once you do it regularly. You get a sense of how much water a plant needs just by looking at it and testing the soil (via moisture meter or just by touch). It's quite rewarding realizing how each plant differs.
allenu··on ASCII and Unicode quotation marks (2007)
Just a guess, but it looks like an IBM Model M but with a German layout, or at least something from that era.
allenu··on Coding after coders: The end of computer programming as we know it?
I was being a little facetious, but there are things that most people would find tedious today that we would put up with in the past. Writing anything long by hand (letters, essays), doing accounting without a spreadsheet, writing a game in only assembly language, using punch cards, typesetting newspapers and books manually...
allenu··on Digg is gone again
I think you're spot on. It feels like parts were edited with AI and parts were left alone.

> This isn't just a Digg problem. It's an internet problem. But it hit us harder because trust is the product.

The statement this is making is presumably the crux of the problem (Digg cannot survive without trust!) but it's worded so poorly that it's hard to imagine someone sat down and figured these three sentences were the best way to make the point.

allenu··on Coding after coders: The end of computer programming as we know it?
I was thinking about that recently. Maybe decades from now people will look at things like the Linux kernel or Doom and be shocked that mere humans were able to program large codebases by hand.
allenu··on Grief and the AI split
I've noticed that too and it's not too different from political discussions. At the end of the day, I think the split is really about different values people have, their identity, and justice.

A lot of developers' identities is tied to their ability to create quality solutions as well as having control over the means of production (for lack of a better term). An employer mandating that they start using AI more and change their quality standards is naturally going to lead to a sense of injustice about it all.

allenu··on Grief and the AI split
> I think the real divide is over quality and standards.

I think there are multiple dimensions that people fall on regarding the issue and it's leading to a divide based on where everyone falls on those dimensions.

Quality and standards are probably in there but I think risk-tolerance/aversion could be behind some how you look at quality and standards. If you're high on risk-taking, you might be more likely to forego verifying all LLM-generated code, whereas if you're very risk-averse, you're going to want to go over every line of code to make sure it works just right for fear of anything blowing up.

Desire for control is probably related, too. If you desire more control in how something is achieved, you probably aren't going to like a machine doing a lot of the thinking for you.

allenu··on Big data on the cheapest MacBook
I was using a M1 Mac Mini and only 8GB of RAM on it to build iOS apps for maybe a year. It's absolutely doable, though it very noticeably gets a little less snappy when building projects. When building in Xcode and then switching to Firefox to browse for instance, I could tell it took slightly longer to switch tabs and YouTube playback would occasionally stutter if too much was happening.

I also was using an Intel MacBook Pro with 16GB at the time. Doing the same thing there was much smoother and snappier. On the whole, it actually made me want to just the laptop instead since it "felt" nicer. (This isn't measuring build times or anything like that, just snappiness of the OS.)

allenu··on Throwing away 18 months of code and starting over
I definitely encountered this second-system effect recently. I have an app that works well because it was written to target a specific use case. User (and I) wanted some additional features, but the original architecture just couldn't handle these new features, so I had to do a rewrite from the ground up.

As I rewrote it, I started pulling in more "nice to haves" or else opening up the design for the potential to support more and more future features. I eventually got to a point where it became unwieldy as it had too many open-ended architectural decisions and a lot of bloat.

I ended up scrapping this v2 before releasing it and worked on a v3 but with a more focused architecture, having some things open-ended but choosing not to pursue them yet as I knew that would just introduce unneeded bloat.

I was quite aware of the second-system effect when doing all this, but I still succumbed to it. Thankfully, the v3 rewrite didn't take as long since I was able to incorporate a lot of the v2 design decisions but scaled some of them back.

allenu··on Darkrealms BBS
I wrote some BBS door games back in the day and was thinking of making a new one today, although not multi-player. It would be in the style of the old games (ANSI-style art and text) but for a single-player and with a daily play limitation as well. You'd only play a few minutes each day and if you died, you'd have to come back the next day. Nothing concrete yet, but I definitely would like to make one just for old time's sake.
allenu··on It took four years until 2011’s iOS 5 gave everyone an emoji keyboard
You're probably right about the terminology being around for a while, but I think most people just called them smileys (i.e. ;) would be called a "winking smiley"). I remember seeing the term used maybe in the early- or mid-90s either on a BBS or Usenet and thinking "Ah, that's what they're called" and as a nerd being annoyed that nobody used that term colloquially.
allenu··on We automated everything except knowing what's going on
Yup. AI can't automate long-term responsibility and ownership of a product. It can produce output quicker but somebody still has to be responsible to the customer using said product. The hard limit is still the willingness of the human producing the code to back what's been output.
allenu··on We automated everything except knowing what's going on
It would be so much easier just to see the three or four bullet points given to the LLM than to read it.
allenu··on Halt and Catch Fire: TV’s best drama you’ve probably never heard of (2021)
I really don't know why this idea still persists that going through App Store review is this awful thing that takes forever and eats up all of your time. It really doesn't nowadays. I've shipped several apps in the last few years and the longest one of my apps has been in review has been maybe 3 days, and the average is between 1-2 days. That's usually for new apps. For updates, it's usually half a day to 1.5 days to get it reviewed.

It takes barely any time to manage the review process. I have had apps and updates rejected but it was easy enough to make some changes and re-submit.

allenu··on Radio host David Greene says Google's NotebookLM tool stole his voice
In the clip, I thought he was playing a prank by reading the script of NotebookLM as the third voice (after the woman). Was that really NotebookLM? I've only heard the first two voices and the first voice didn't sound like him to me, but the last one definitely sounded like him.
allenu··on You can't trust the internet anymore
I think before Friendster, Myspace, then Facebook, there was a period where there were discussion forums for local communities. I think it was useful for meeting people. I remember friends in the late '90s used them frequently for chatting and some made new friends in real life that way. It was a short period, though, as more established companies came along that had a wider reach.
allenu··on You can't trust the internet anymore
I agree. It's not that the web was high-trust. It was more that if you landed on a niche web page, you knew whoever put it together probably had at least a little expertise (and care) since it wouldn't be worth writing about something that very few people would find and read anyway. Now that it's super cheap to produce niche content, even if very few people find a page, it's "worth it" to produce said garbage as it gives you some easy SEO for very little time investment.

The motivation for content online has changed over the last 20 years from people wanting to share things they're interested in to one where the primary goal is to collect eyeballs to make a profit in some way.

allenu··on My AI Adoption Journey
I agree that framing and scoping tasks is becoming a real joy. The great thing about this strategy is there's a point at which you can scope something small enough that it's hard for the AI to get it wrong and it's easy enough for you as a human to comprehend what it's done and verify that it's correct.

I'm starting to think of projects now as a tree structure where the overall architecture of the system is the main trunk and from there you have the sub-modules, and eventually you get to implementations of functions and classes. The goal of the human in working with the coding agent is to have full editorial control of the main trunk and main sub-modules and delegate as much of the smaller branches as possible.

Sometimes you're still working out the higher-level architecture, too, and you can use the agent to prototype the smaller bits and pieces which will inform the decisions you make about how the higher-level stuff should operate.

allenu··on Swift in the Browser with ElementaryUI (Swift FOSDEM 2026 Talk) [video]
I agree the language itself has gotten more complex, but for day-to-day productivity in terms of actually using it to write code, I don't think it makes a difference.

I've found writing Swift code very pleasant, but I've been doing it for ten years, so that helps I suppose. The biggest productivity impact for day-to-day use for me in the last few years has been the new concurrency model.

allenu··on AI’s impact on engineering jobs may be different than expected
I don't think it necessarily scales that way. Larger organizations need more communication channels and coordination. If anything, assuming AI does give you 10x ability, there's probably a sweet spot where you have just enough developers that churn out code at a good pace but not too many that it gets too chaotic.

If you compare one developer to 10, for instance, one developer doesn't have to deal with communicating with 9 other people to make sure they're working on things that align with the work everyone else is doing. There is no consensus that has to be reached. No meetings, no messages that have to be relayed, no delays because someone wasn't around to get approval. That one developer just makes a decision and does it.

There are lots of big companies out there and in the past, small startups have been able to create successful products that never would have been created at the big company even though the big company hired way more developers.

← PreviousPage 2 of 32Next →