At last a sane person. Logs are for identifying the event timeline, not to acquire the whole reqs/resp data. Putting every detail into the logs is -in my experience - makes undertanding issues harder. Logs tell a story. When, what happened, not how or why that happened. Why is in the code, how is in the combination of, data, logs, events, code.
And loosely related, I also dislike log interfaces like elk stack. They make following track of events really hard. Most of the time you do not know what you are loooking for, just a vauge understanding of why you are looking into the logs. So a line passed 3 micro seconds ago maybe your euraka moment, where no search could identify , just intuition and following logs diligently can.
A music player for my 2 years old son. There are premade toys like Yoto player. But what is the fun in buying ready made?
esp32+sdcard reader+gc9a01 lcd and a pcm5102a+xh-a232 (overkill 30W! solution! Will replace in time)
Add some 3d printed enclosure and you are done. I am currently vibe coding a UI into it. I am planning to cram in adsp Bluetooth speaker support and some web config, maybe ota updates..
Cool. I'd like to try something similar. Does that amplifier module drive headphones as well? What future replacement do you have in mind? Is it all low power enough to use a battery?
For a headphone you do not even need the amp. The pcm5102a purple module can directly use headphones. Mine already has a 3.5 jack . It has been a life saver for devlopment at night.
I am planning to replace the amp with a Pam84xx and switch to a smaller/thinner speaker to save space.
I may also add a nfc reader module to add nfc card music. Probably card will include a url to download music file.
Also my protoboard based solution is finicky. I starded building a pcb, however as this is my first pcb project I am taking it real slow.
Perhaps I can open a git repo to document share what I have.
Oh interesting. The datasheet for the PCM5102A says it supports line-level output with a minimum load of 1kΩ [1]. I think most headphones typically have an impedance of less than 100Ω. I'd guess the excess current results in some distortion or low volumes? It works fine in practice though?
With so many hearing aid users around, this may be the perfect time for me to ask what it is like to wear one, and how it improves dayly life.
I have some hearing loss (suppose moderate) only in my left ear. As this is only on single one I think I am coping enough with the right for now. With regular "ha , sorry, what?" moments.
In your experience should I be investing in one immediately or trying my best with current coping situation for now?
I also have hearing loss in one ear. I have a hearing aid for that ear, and it dramatically improves my higher-frequency hearing on that side. My wife certainly appreciates it. If I start speaking loudly, she will often say, "Do you have your hearing aid in?", and either I forgot to wear it or the battery is dead (typically lasts about 16 hours).
One drawback is that I can't listen to Bluetooth music because it only comes through the one side. It's good enough for podcasts, through.
Mine is a Costco one (manufactured by Phonak, I believe). Nothing really fancy, but only $1,000 -- and the Ontario government covered half of that.
I kind of resisted getting a hearing aid for a long time -- even though I used to date an audiologist -- but it's a significant improvement to my quality of life.
I still can't believe that we are in the era of 'star trek' like "Computer plot me a proof for this math problem" in my life time! Wish we could also do the same for "Beam me up scotty"
Thinking about such questions before we are capable of doing such an experiment at least with small animals is like discussing how many angels can stand on the point of a pin.
Inventing a Star Trek-style teleporter would be quite something, but I
don't see how it would advance the philosophy in any way. We already know
the teleportation subjects would report 'feeling just the same' as before.
If they didn't then by definition it's not a functioning teleporter, as it
accidentally modified the subject in transit.
I feel odd about "bug fixing" to be a special occasion than being the work. Features need to be added, so do bugs need to be fixed. Making it a special occasion makes it feel like some very low priority "grunt work" that requires a hard push to be looked at.
I suppose all comes down to who runs the leading (or any) investment companies. Money people are not known to be technically literate enough for not being fooled by magic (any sufficiently advanced technology).
They are facinated by llms that they are pouring down money to AI related companies. Can you blame them? Can’t deny, I am also fascinated by llms.
> They are facinated by llms that they are pouring down money to AI related companies. Can you blame them? Can’t deny, I am also fascinated by llms.
I don’t think they’re fascinated by LLMs in the way the average Hacker News user is. They are fascinated by the pipedream (intended) of LLMs enabling them to lay off masses of workers and having AI do the work instead. It fascinates them the same way offshoring has fascinated them for years.
Most of the time discussion derails as everyone is focusing on different aspects of the experience.
When you look into all the complaints one by one they are exceptionally acurate.
* yaml has its quirks. - check
* text templating can’t be validated for spec comformity - check
* helm has lot’s of complexity - check
* helm has dependency problems - check
* helm charts can have too many moving parts with edge cases causing deep dive in the chart - check
and many others. However proposed solutions cut short on providing the value helm brings on.
Helm is not just a templating engine to provide kubernetes manifests. It’s an application deployment and distribution ecosystem. Emphasis on the "ecosystem".
* It brings dependency management,
* It provides kubernetes configuration management.
* It provides abstraction over configuration to define applications instead of configuration.
* It provides application packaging solution.
* It provides an application package manament solution.
* There is community support with huge library of packages.
* It’s relatively easy to create or understand charts with a varied experience level. A more robust and strictly typed templating system would remove at least half of this spectrum.
* The learning curve is flat.
When you put all of these in to consideration, it’s relatively easy to understand why it’s this prominant in the kubernetes ecosystem.
And loosely related, I also dislike log interfaces like elk stack. They make following track of events really hard. Most of the time you do not know what you are loooking for, just a vauge understanding of why you are looking into the logs. So a line passed 3 micro seconds ago maybe your euraka moment, where no search could identify , just intuition and following logs diligently can.