Building in NY. Dicklesworthstone has 179 repositories available. Follow their code on GitHub.

People think they can use Fine-Tune for Knowledge Injection. People are Wrong

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

If fine-tuning is a risky solution, what’s the alternative? The answer lies in modularity and augmentation. Techniques such as retrieval-augmented generation (RAG), external memory banks, and adapter modules provide more robust ways to incorporate new information without overwriting the existing network’s knowledge base.

Free image background removal - private, client-side and powered by Transformers.js - addyosmani/bg-remove

https://bg.addy.ie/

Googles system prompt of the CLI is heavily flawed IMO. That's where most problems arise. I am using a custom one. At least it is highly configurable. The vanilla Gemini Cli is not usable for me. For instance, they have a section they introduce with Proactiveness where they give advice about what is Persistence (in the agent loop). This wrong wording alone causes the agent to be "proactive" in many ways that is not wanted. After I asked the model itself once, why it started to scan my entire codebase when I just asked to create a new branch, it directly said to me there is "Proactiveness" in its system prompt. I was baffled, why would anybody want that? So i digged deeper and did also a thorough analysis with Opus 4.7 of just this system prompt file - that cost me an entire Pro-session btw. - and documented the results in this pr: https://github.com/google-gemini/gemini-cli/pull/26129 - I am using the optimized prompt and had no issues so far I had with the original one.

Another big issue is "model panic" - the Gemini model often overwrites entire files "from memory" with write_file, when the edit tool fails 2 times. That occasionally causes code degradation, and when there are multiple turns and there is no backup, the model starts to get nuts, trying to fix its errors, and destroys even more in the effort to just make it compile / build. I gave it a rotating pre-write backup and a restore_file tool. The model panic vanished. https://github.com/google-gemini/gemini-cli/pull/25947

With these two fixes, Gemini CLI is pretty good - without them I wouldn't use it.

For all of the AI industry’s advancements, the major models like ChatGPT and Claude still struggle with PDFs, one of the oldest and ubiquitous file formats.

Building a fully functional, code-editing agent in less than 400 lines.

I have literally never seen LLM writing that actually improved my life.

The model produces better work. Some of my peers believe that large language models produce strictly better writing than they could produce on their own. Anecdotally, this phenomenon seems more common among English-as-a-second-language speakers. I also see it a lot with first-time programmers, for whom programming is a set of mysterious incantations to be memorized and recited. I think this is also the cause of language model use in some forms of academic writing: it differs from the prior case with paper reviews in that, presumably, the authors believe that their paper matters, but don’t believe they can produce sufficient writing

How I use AI as a design engineer on a daily basis.

I work to bring AI into production. I write about AI system design.

When performing multi-turn operations (specifically Function Calling), the client must pass this signature back in the subsequent request. This ensures the model resumes execution from the exact state where it halted, rather than re-computing context from the raw message history. Omission results in an invalid_argument error or non-deterministic behavior.

You don't need Elasticsearch for most projects. I built a simple search engine from scratch that tokenizes everything, stores it in your existing database, and scores results by relevance. Dead simple to understand and maintain. - Build it yourself

Embeddings are a really neat trick that often come wrapped in a pile of intimidating jargon. If you can make it through that jargon, they unlock powerful and exciting techniques …

Stanford's Jeremy Utley reveals that "most people are not fully utilizing AI's potential." Why is that? He explains that it lies in how we approach AI. He said a simple mindset shift could be what you've been missing in the AI revolution.

Creativity is doing more than the first thing you think of

Think of LLM as a teammate and not just a tool. Provide it feedback! Let it ask you questions!

Key Insights:
📌How treating AI as a teammate rather than just a tool can dramatically improve outcomes
📌Why you should have AI ask you questions instead of just answering yours
📌How non-technical professionals can leverage AI to achieve extraordinary results
📌The difference between treating AI as a tool versus as a teammate

00:00 Intro

If you want to learn more about creativity using AI with Professor Jeremy, please refer to the link below!
👉 https://www.jeremyutley.design/ai-newsletter

We have decades of experience trying to automate processes. The biggest lesson is that automation is not about the easy and known flow, but about exception handling.

The best diagnosis for exception handling I can think of is to wait on line at the post office. If you’ve ever done that, you know the thought of “doesn’t anyone just want to mail a package” comes to mind. As it turns out the entire flow at the post office (or DMV or tax office) is about exception handling. No amount of software is going to get you out of there because it is piecing together a bunch of inputs and outputs that are outside the bounds of a system.

The ability to automate hinges not just on the ability to know the steps to take for predefined inputs, and not even the steps to take if some inputs are erroneous or incomplete, but what to do if you can’t even specify the inputs.

My favorite example of the latter is how the arrival of IBM computing in the 60s and 70s totally changed the definition of accounting, inventory control, and business operations. Every process that was "computerized" ultimately looked nothing at all like what was going on under those green eyeshades in accounting. Much of the early internet (and still most bank and insurance) look like HTML front ends to mainframe 3270 screens. Those might eventually change, just not quickly. It might be that the "legacy" or "installed base" of many processes is such that the cost to change is too monumental.

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

Back in January, I wrote a blog post about adding JSON-LD to your web pages to make it easier for Google to understand what they were about. The example I used was my ReadABooker site, which encourages people to read more Booker Prize shortlisted novels (and to do so by buying them using my Amazon

It was like a revelation when chain-of-thought AI became viral news as a GitHub project that supposedly competed with SOTA's with only 2 developers and some nifty prompting...
Did all the companies just jump on the bandwagon an weave it into GPT/ Gemini / Claude in a hurry?
Did those companies already have e.g. Gemini 2.5 PRO thinking in development 4 months ago and we didn't know?

*if you include word2vec.

https://jaketae.github.io/study/word2vec/#testing-the-model

For tech and AI talent, jobs at financial services companies are more desirable than they have ever been. Banks have been working hard to make it happen.

Build your next presentation in minutes with our free slide templates! No matter what you’re creating, Beautiful.ai has the template for you.

Why LLMs will transform development but not how you think

it's about how AI tools are enabling a new category of software that simply couldn't exist before.

When someone can describe their specific needs conversationally and receive working code in response, the economics of personal software development shift dramatically.

Think of it this way: just as spreadsheets enabled non-programmers to perform complex calculations and data analysis, AI-assisted development tools are enabling non-programmers to create personal software solutions.