baijum

I have never worked on Android and iOS app development before. But with the help of AI, it seems that almost anyone can build an app today.

This is my first mobile app, created with the assistance of AI: https://baijum.github.io/ukulele-companion/

Interestingly, I don’t know Kotlin, Swift, iOS, or Android development. And for that matter, I’m not even a musician!

This app is a companion tool for the ukulele, a music instrument I recently started learning. Building it was a fun experiment to see how far AI-assisted development can go.

It’s amazing how accessible software creation is becoming.

Based on the feedback, I have created a page: https://towlion.github.io/platform/scope/

Built Ukulele Companion, an open-source Android app for learning Ukulele, with AI. It includes fretboard/chords/tuner/scales/progressions and is fully offline, ad-free, and no-tracking. Would love feedback on practical workflows for keeping AI-generated code clean and maintainable.

I built Prompter to help automate repetitive code maintenance tasks using Claude AI. It lets you define workflows in TOML files that can execute sequentially or conditionally based on task outcomes.

Key features: - AI-powered project analysis that generates initial configuration - Session resumption to maintain context across complex tasks - State tracking for interrupted workflows - Support for Python, JavaScript, Rust, Go

Example use case: You can create a workflow that updates deprecated APIs, runs tests, and only proceeds to the next modernization task if tests pass. Each task can retry on failure or jump to a different task based on the outcome.

The tool uses the Claude SDK to execute tasks while maintaining context between steps. It's particularly useful for large-scale refactoring, security updates, or incremental code quality improvements.

Would love feedback from anyone dealing with technical debt or large codebases that need systematic updates.

Disclaimer: This project is developed using Claude Code.

This project could be one option for new languages: https://genlm.org/genlm-control/

That's a very fair and critical point. You're right that we can't change the fundamental, probabilistic nature of LLMs themselves.

But that makes me wonder if the goal should be reframed. Instead of trying to eliminate errors, what if we could change their nature?

The interesting hypothesis to explore, then, is whether a language's grammar can be designed to make an LLM's probabilistic errors fail loudly as obvious syntactic errors, rather than failing silently as subtle, hard-to-spot semantic bugs.

For instance, if a language demands extreme explicitness and has no default behaviors, an LLM's failure to generate the required explicit token becomes a simple compile-time error, not a runtime surprise.

So while we can't "fix" the LLM's core, maybe we can design a grammar that acts as a much safer "harness" for its output.

Probably Red Hat Universal Base Image would be good enough for development instead of waiting for CentOS; https://www.redhat.com/en/blog/introducing-red-hat-universal...

There is no photo of the mathematician in the Wikipedia page!

OP here. I posted this here with the exception of getting more feedback on the topic. Thanks!

Another book: http://cvs.savannah.gnu.org/viewvc/*checkout*/softfree/softf...

I remember reading this article long back: http://www.free-soft.org/FSM/english/issue01/bob.html

This issue has been fixed in upstream. https://issues.jboss.org/browse/RHDENG-1320 Please try it again after some time.

There is video link in this blog post: https://developers.redhat.com/blog/2017/05/02/announcing-red...

Sorry for the inconvenience! I have reported this issue here: https://github.com/openshiftio/openshift.io/issues/134

The upstream for openshift.io is primarily in the fabric8 project. fabric8 is found in the following organizations:

https://github.com/fabric8io https://github.com/fabric8-ui https://github.com/fabric8-analytics https://github.com/fabric8-quickstarts https://github.com/fabric8io-images

Official announcement: https://www.redhat.com/en/about/press-releases/red-hat-unvei...

More info about GC changes in 1.5:

https://talks.golang.org/2015/state-of-go-may.slide#6 (Slides 6 to 11)

https://golang.org/s/go14gc

I submitted this news few hours back with that title based on the tweet:

https://news.ycombinator.com/item?id=9812968

Edit: not exact same title, but similar.