At least this story shows that the lack of greed didn't improve quality.
536 karma · joined July 19, 2017
My key focus is helping organizations do security better, make it simpler, and get alerted when things get messy.
At least this story shows that the lack of greed didn't improve quality.
Even the random hex with checksum component seems overkill to me, either the API key is correct or it isn't.
If we can centrally manage her bookings and all she has to do is look at the calendar and clearly see what is happening today, and in the near future, there is a real use-case for that.
Especially as I don't live near her, and remotely managing a calendar in her house would be amazingly useful.
Triple check the security side of things.
Accuracy is important if you want people to give you money.
I saw a BBC? documentary about this years ago and it showed how some cultures had the ability to clearly identify different colours where I couldn't see any difference.
It turns out that knowing subtle differences in colours can have a strong impact on your daily life, so cultures pick unique parts of the colour spectrum to assign names to.
e.g. high RPM, or high torque options over existing generators?
Some products have these fancy KQL style search parameters but if you forget to 'save the search' within the applications 'Save Search' facility, then when you duplicate a tab the search is lost.
It feels rude when sites ignore the UX improvement by not leveraging the power of URLs to store current state.
Even if a little of everyone's day consumes AI services, then the investment required will be immense. Like what we see.
One thing I've noticed is that I don't have a circle of people where I can discus programming with, and having an LLM to answer questions and wireframe up code has been amazing.
My job doesn't require programming, but programming makes my job much easier, and the benefits have been great.
But liquid glass is such a horrible idea for a UI!
Now I feel like an old person, but I live with glasses every day and absolutely love clean UI's.
Introducing glass lens f*ckery just for the sake of it is terrible.
This means, if you turned animations off you would still work as fast and understand the flow the same as if animations were enabled.
For me, the purpose of animations is to soften the UX journey, and to confirm what I already knew, by giving me small indications that yes, the UI is truly in the state I expect it to be.
Such as fast highlighting of on hover items, so I don't have to correlate the mouse position to the control.
I love that example of tool tip popups taking 0ms once you have popped up one, that is a clear signal that the UX understands you are trying to learn more about the controls you're hovering over.
That's a perfect representation of how animations signal understanding of your UX journey.
When an API commits to /v1 it doesn't mean it will deprecate /v1 when /v2 or /v3 come out, it just means we're committing to supporting older URI strategies and responses.
/v2 and /v3 give you that flexibility to improve without affecting existing customers.
I'm sure people complained that hammers were a useless invention and why would anyone not want to keep using rocks.
If knowledge and experience in the language is an issue, then LLMs have increased value as they can teach you language notation as well as do the mundane stuff.
If understanding good programming architecture / patterns is an issue, then you have to be more careful with the LLM as you are listening to advice from something that doesn't understand what you really want.
If understanding how to guide an LLM is an issue, then you have to work, test, and design ways of building guidelines and practices that get the outcomes you want.
Using LLMs to code isn't some cheat-code to success, but it does help greatly with the mundane parts of code if you know how to program, and program well.
How much of a large project is truly innovation? Almost every application has boilerplate code wrapped around it, error handling, CRUD endpoints, Web UI flows, all stuff you have to do and not really the fun stuff at the core of your project.
This is where I find LLMs shine, they help you burn through the boring stuff so you can focus more on what really delivers value.
It feels physically jarring when it loses the plot with a conversation, like talking to someone who wasn't listening.
I'm sure its a tuning thing, I hope they fix it soon.
Try
It also takes a while to learn using an LLM and get value from it.
The keys are how to build prompts, ways of working, and guidelines that help the AI stay focused.
You end up spending much more time guiding and coaching rather than coding, that can take a while to get used to.
Eventually though, you will master it and be able to write secure, fast code far beyond what you could have done by yourself.
Note: Also, prep yourself for incoming hate every time you make claims like that! If you write bad code, it's your fault. If your LLM writes bad code, you're a moron! hah
It seems to lose the thread of the conversation quite abruptly, not really knowing how to answer the next comment in a thread of comments.
It's like there is some context cleanup process going on and it's not summarizing the highlights of the conversation to that point.
If that is so, then it seems to also have a very small context, because it seems to happen regularly.
Asking it to 'Please review the recent conversation before continuing' prompt seems to help it a bit.
The point that I'm probably missing (and others) is that we associate the phrase 'Vibe Coding' with 'Using an LLM to help with coding' and they're not the same.
Maybe the critics of Vibe Coding need to remember that all users of LLMs for coding support aren't about to regret their life choices.
I'm a heavy user of Claude Code and I use it like a coding assistant.
How well you can manage a development team in real life has strong correlations on how much value you get out of an LLM based coding assistant.
If you can't describe what success looks like, expect people to read your mind, and get angry at validating questions, then you will have problems both with coding assistants and leading teams of developers.
It's no different to vibe coding, except if you ask an LLM to harden your code base to pass a pen test, it will do something.
Enterprises just don't give a sh!t.
I wonder if they design in flow channels for the heavier CO2 to flow down to safe, unpopulated areas.
We don't log just to have records of everything, we log to solve future questions.
I'm working on a system that generates huge numbers of log entries and have settled on a short term solution to over log everything.
Once a log entry has persisted, I'm using it as a 'Bronze Layer' in a typical Medallion Model and will then filter that log data up into Silver and Gold layers so I can have billing, reporting, dashboard metrics being lifted out of the verbose logs.
Not sure what I'll do with the verbose Bronze Layer logs maybe cold store them somewhere, but it's interesting to experiment with progressive aggregation of logs to hopefully purge and dispose of the raw log data as fast as we can extract value.