I agree, though I would prefer to highlight the first half of the first item - transparency. Also, perhaps make Safety an independent principle than combining with Security.
These are a good set of principles for any company (or individual) can follow to guide them how they use AI.
I agree - the content you write about LLMs is informative and realistic, not hyped. I get a lot of value from it, especially because you write mostly as stream of consciousness and explains your approach and/or reasoning. Thank you for doing that.
Congrats — well deserved! I love the game and play it every day; it's actually the first thing I do in the morning. A big fan of Hard mode! My best friend has also started playing it and we share the results with each other.
Just one feedback - on desktop browsers, I can see the list of answered clues below the textbox, but on the phone (Brave or Firefox on Android), I don't see that list. I am not sure if this is a feature or a bug, but it’s a feature I miss when playing on my phone. Seeing those answers gives that little “aha!” moment of satisfaction.
I also made a custom GPT - Bracket GPT [0] that helps in solving the clues when I am stuck. It doesn’t directly give the answers, but offers hints to help nudge you to the solution. It’s a fun companion when you're totally blanking.
This! I love the pure joy of picking both the destination and the path. No pressure, no goal — just the joy of building for its own sake.
These two lines really hit home:
> You don’t have to listen to any other voices here, except that quiet one inside of you that’s gently urging you to do the thing you know you need to do.
> You don’t need to know where it’s going to lead. For that matter, it doesn’t have to lead anywhere. Nothing ever has to come of it.
That freedom is everything. Just creating because it feels right (to me).
I experimented with vibe coding [0] yesterday to build a Pomodoro timer app [1] and had a mixed experience.
The process - instead of typing code, I mostly just talked (voice commands) to an AI coding assistant - in this case, Claude Sonnet 3.7 with GitHub Copilot in Visual Studio Code and the macOS built-in Dictation app. After each change, I’d check if it was implemented correctly and if it looked good in the app. I’d review the code to see if there are any mistakes. If I want any changes, I will ask AI to fix it and again review the code. The code is open source and available in GitHub [2].
On one hand, it was amazing to see how quickly the ideas in my head were turning into real code. Yes reviewing the code take time, but it is far less than if I were to write all that code myself. On the other hand, it was eye-opening to realize that I need to be diligent about reviewing the code written by AI and ensuring that my code is secure, performant and architecturally stable. There were a few occasions when AI wouldn't realize there is a mistake (at one time, a compile error) and I had to tell it to fix it.
No doubt that AI assisted programming is changing how we build software. It gives you a pretty good starting point, it will take you almost 70-80% there. But a production grade application at scale requires a lot more work on architecture, system design, database, observability and end to end integration.
So I believe we developers need to adapt and understand these concepts deeply. We’ll need to be good at:
- Reading code - Understanding, verifying and correcting the code written by AI
- Systems thinking - understand the big picture and how different components interact with each other
- Guiding the AI system - giving clear instructions about what you want it to do
- Architecture and optimization - Ensuring the underlying structure is solid and performance is good
- Understand the programming language - without this, we wouldn't know when AI makes a mistake
- Designing good experiences - As coding gets easier, it becomes more important and easier to build user-friendly experiences
Without this knowledge, apps built purely through AI prompting will likely be sub-optimal, slow, and hard to maintain. This is an opportunity for us to sharpen the skills and a call to action to adapt to the new reality.
This was super fun! The bracket format is brilliant. It's like going on a treasure hunt, you solve one clue and the next one reveals itself. Well done!
Very true. Filling the time with non-scrolling enjoyable activities, particularly IRL is effective. It's like eating healthy - rather than stressing about what to remove from the plate, think about what you want to add to the plate and enjoy it.
1) Amen 2) I wonder if this is isolated to junior dev only? Perhaps it seems like that because junior devs do more AI assisted coding than seniors?