|
My starting word is ADIEU.
|
|
|
|
|
I often use EARLY for the same reason, also many words end in Y, LY or RLY
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
OriginalGriff wrote: TINEA, AEROS and ARISE I only know 1/3rd of those words
Used ALIVE today (as I misremembered ARISE) and got it in four tries.
Used RUINS before that, all much used letters.
I'll throw in an EPOXY once in a while, as that was the solution about two weeks ago and it has XY.
All in all, I find it very hard to come up with English words, even when I have most of the letters.
|
|
|
|
|
Wordle 293 3/6
β¬π¨π©β¬β¬
π¨π¨π©π¨β¬
π©π©π©π©π©
|
|
|
|
|
Would have been 3 in easy mode.
Wordle 293 5/6
π©β¬π©π©π©
π©β¬π©π©π©
π©β¬π©π©π©
π©β¬π©π©π©
π©π©π©π©π©
|
|
|
|
|
I have a couple of console tools that emit C or C++ header files to stdout.
On Windows 10 and prior, I'd redirect to the console using > but the file it created was always UTF-16 which my compilers don't like. So I would have to open in notepad and save as, select UTF-8 and then overwrite.
It's an annoyance I have gotten so used to that I went to do the same thing on win11 (i thought the file looked kinda small) and lo and behold! it was already in UTF-8. Woot.
Thank you, Microsoft for actually making substantial, if easily missed improvement to Windows.
To err is human. Fortune favors the monsters.
|
|
|
|
|
I get UTF-8 in the Win 10 console all the time.
|
|
|
|
|
Well you must be doing something different, or running a different build or edition of windows, because this will do utf-16 on a fresh install of home 10 every single time.
Edit: Obviously if you fiddle your results may change, but there are problems with fiddling in that the windows console is notoriously buggy.
So I'm not talking about post-tweaking. I'm talking about unboxing windows, writing a C++ app that printfs to stdout, Win+R, cmd.exe, type foo.exe > bar.txt
it will gen utf-16
To err is human. Fortune favors the monsters.
|
|
|
|
|
|
honey the codewitch wrote: On Windows 10 and prior, I'd redirect to the console using > but the file it created was always UTF-16 Hmm. I've never had Windows create a UTF-16 file when redirecting stdout. I don't think the fact that you've been getting UTF-16 files has been Windows' fault but a result of the tools doing UTF-16 output.
It's possible that the 'fix' you are seeing is an enhancement in Windows detecting UTF-16 output and automatically converting it to UTF-8 for the console to improve readability.
Software Zen: delete this;
|
|
|
|
|
weird. well, no bother now. it's doing it right.
To err is human. Fortune favors the monsters.
|
|
|
|
|
I just got a message from friend from Kyiv.
He's had to vacuate and is very worried about friends and family. He's witnessed the Russian brutality and determined to fight untill his homeland is taken back.
He's OK for now, but they need our support to keep fighting!
|
|
|
|
|
I previously rebooted the documentation for GFX - index.md[^]
What I didn't have were unit tests, for a number of reasons, chief among them I didn't know how to convince platformIO to use them, particularly in the somewhat complicated scenario I need them to work in (my library has dependencies of dependencies for example), but also because I had no CI/CD infrastructure to run them in the first place and it's already a ton of work to publish - begging the need for CI/CD.
With *a lot* of help I got all of the above in place now, but I am stuck writing unit tests now. Since the library is already somewhat mature I have lot of ground to cover. It's hard to keep track.
But wait!
My documentation has a handy outline, aka a table of contents.
There's the outline for my unit tests.
Now I have something to go on. I can just write the tests following the documentation. That will at least cover the surface area of my code.
It's not an especially clever thing, as clever things go, but it's saving me a ton of time, and getting my feet under me so yay.
To err is human. Fortune favors the monsters.
|
|
|
|
|
Why are all my messages being flagged for review? I always follow the rules.
|
|
|
|
|
9 messages and rep points of 719. not sure if that factors into the algorithm they use.
you have been a member for 6+ years.
I think after a certain level your messages aren't flagged anymore, but I could be mistaken.
|
|
|
|
|
Hey Walt,
It's great to see you again. You should ask a staff member to help you recover your old account[^].
Best Wishes,
-David Delaune
|
|
|
|
|
I thought his name sounded familiar. Good catch.
|
|
|
|
|
See that also on your latest message. Of course I remember you 'junior' and don't remember that was the case (flagged) in past.
Maybe CP AI changed ....
|
|
|
|
|
Bob probably didn't like the cut of your jib and marked you for termination.
To err is human. Fortune favors the monsters.
|
|
|
|
|
Documentation AND unit tests?!??!????
And you call yourself a developer!π€ͺ
If you can't laugh at yourself - ask me and I will do it for you.
|
|
|
|
|
DRHuff wrote: And you call yourself a developer! Harrumph. Those of us who regularly and consistently document and test what we develop find it disheartening when the rest of you don't follow our example.
Especially when we have to use your crap.
Software Zen: delete this;
|
|
|
|
|
I don't know. I definitely appreciate unit testing, but I'll take a mature library if it's documented, even if the testing wasn't the most rigorous. "battle tested/field tested" counts for something, in my book. I'm not saying it's ideal, but it's not nothing.
To err is human. Fortune favors the monsters.
|
|
|
|
|
I agree with Honey somewhat. She is definitely a developer.
If one's software is guiding a missile, flying an airplane, doing surgery, or powering a city, then rigorous unit testing is a requirement.
If it's a library for open ended usage, then proper documentation and user feedback for bugs, etc. should be part of it. Much like open source, etc. Maturity is also a key factor. How long has it been used and what is its track record, etc.
I've done a little of both. Validation and verification processes defined and executed when being actively used for work.
Like factory inventory, bookkeeping, etc. Even the big companies fall on their faces if they do not do this. Read where big name car rental company caused people to be arrested and jailed because their software did not properly reconcile whether a car was lost or actually stolen. Yikes.
|
|
|
|
|
jmaida wrote: their software did not properly reconcile whether a car was lost or actually stolen. Yikes.
Yikes indeed!
I totally agree with all of what you said in your post above. I guess I just didn't really kick it around much before I posted.
To err is human. Fortune favors the monsters.
|
|
|
|
|