|
Three for me:
Wordle 381 3/6
⬜🟩⬜🟨⬜
⬜🟩🟨🟩🟨
🟩🟩🟩🟩🟩 But I got lucky - there were quite a few options for that last one!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Wordle 381 6/6
⬜⬜⬜⬜⬜
⬜⬜⬜🟨⬜
🟨🟨🟨⬜⬜
⬜🟩🟨🟨⬜
🟩🟩🟨🟨🟩
🟩🟩🟩🟩🟩
Just made it
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Wordle 381 5/6
⬜⬜🟨⬜⬜
⬜🟨🟨⬜🟨
⬜🟨🟨⬜⬜
⬜🟩🟨🟨🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 381 4/6
🟨⬜🟨⬜⬜
🟨⬜🟨🟨⬜
🟩🟩🟩⬜🟩
🟩🟩🟩🟩🟩
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
Wordle 381 3/6
⬜🟨⬜⬜⬜
⬜🟩⬜🟨🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 381 3/6
🟨⬛⬛🟩⬛
⬛⬛⬛🟩🟩
🟩🟩🟩🟩🟩
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
|
|
|
|
|
Wordle 381 4/6*
⬜⬜🟩⬜⬜
⬜⬜🟩⬜🟩
⬜🟩🟩🟩🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 381 5/6*
⬜⬜🟩⬜⬜
⬜🟨🟩⬜⬜
🟨⬜🟩⬜⬜
🟨⬜🟩🟩⬜
🟩🟩🟩🟩🟩
Almost lost!
Happiness will never come to those who fail to appreciate what they already have. -Anon
|
|
|
|
|
Wordle 381 3/6
⬛⬛⬛⬛🟨
⬛🟩🟩🟩🟩 😲
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 381 5/6
⬛⬛⬛⬛⬛
⬛⬛🟨⬛🟨
⬛🟩🟨🟨⬛
⬛🟩⬛🟨🟩
🟩🟩🟩🟩🟩
Get me coffee and no one gets hurt!
|
|
|
|
|
Could some of you guys share a bit about your projects that use logging (not as a debugging process component but as a normal way of application functioning) and the type of things you throw in your logs. I would like to find out about all types of software that does some type of logging, everything ranging from desktop apps to servers. Thanks
|
|
|
|
|
Generally speaking, I use logs for open fires and camping.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Quote: open fires
I imagine you use logs made of wood to keep the fire burning and (for) other leasure activities around the camp.
|
|
|
|
|
If they are big enough, you can sit on them as well!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
camping or trip chairs and tents are my favorites.
modified 4-Jul-22 15:27pm.
|
|
|
|
|
If you are camping by car, then yes. But on a bike, A tent is a necessity (and the rest of the space is free for food and beer)
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
We do a lot of ETL work. Each ETL task takes a different amount of time. We use the logs to calculate the average time for each task to aid in scheduling the next run -- and thereby perform the historically longest-running tasks first.
Similarly, we track record counts and signal an error if a record count falls outside the expected range ( +/- some factor).
|
|
|
|
|
Thanks Piebaldconsult I had to check online the ETL abbreviation for its meaning. That`s field I wasn`t familiar with.
|
|
|
|
|
This is such an insanely huge topic of discussion.
Here's what we do:
- Every exception thrown in our code gets logged
- When we fix a bug that's due to odd input or conditions we generally log the odd condition up to the point where it's common enough we feel we have a handle on it's many guises
- When there's a spot where the code simply cannot, ever, in a million years be reached, and it's reached, we log it.
- When there are failures of external services we might log them in order to work out what conditions will cause it to fail so we can work on preemptively not causing those conditions
- When conditions in our app become extreme (eg serious user load, serious queue back-ups etc) we log them
Some of these logs are for debugging, some for planning, some of these logs are used to trigger alerts, and some for our own amusement.
cheers
Chris Maunder
|
|
|
|
|
Don't you just wish you could have a loonie for every time bullet point 3 has happened?
Shoot, I could have wound up chasing Elon Musk in the Forbes 500.
|
|
|
|
|
I know, right? And you stare and you stare, and you run every test and scenario and it's simply, positively, absolutely impossible.
And blip. Another log entry pops up.
cheers
Chris Maunder
|
|
|
|
|
Seen this too many times to count. Unbelievably frustrating at times.
|
|
|
|
|
We've had similar situations in so many oddball scenarios I added a dynamic counter window to our tracing app. Rather than watching for an event to go flying by(*), it's easier to see the count increment.
(*) Our product is multicomputer, multiprocess, and multithreaded. Our logging records hundreds or even thousands of events per second, depending on what the thing is doing.
Software Zen: delete this;
|
|
|
|
|
Agree. Huge topic of discussion. Lots of requirements, lots of conditions, and even more requirements.
Start with first order requirements, such as source, frequency, etc.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Sorry not much to add. Chris said it all.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|