|
Wordle 618 3/6*
⬜🟨🟨🟩🟩
⬜🟩🟩🟩🟩
🟩🟩🟩🟩🟩
Good starter, lucky third guess!
"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 618 4/6
🟨⬛🟩⬛⬛
⬛🟩⬛⬛⬛
⬛🟩🟩⬛🟩
🟩🟩🟩🟩🟩
Finally a smooth run after a while.
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
|
|
|
|
|
⬜🟨⬜⬜🟩
⬜⬜🟩⬜🟩
⬜⬜🟩🟩🟩
⬜🟩🟩🟩🟩
🟩🟩🟩🟩🟩
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 618 6/6
🟨⬜⬜⬜🟨
⬜⬜🟨⬜🟨
⬜🟩🟨🟨🟨
🟨🟩⬜🟨🟨
🟨🟩⬜🟨🟩
🟩🟩🟩🟩🟩
Phew!
|
|
|
|
|
Wordle 618 5/6*
🟨⬜🟨⬜⬜
⬜🟩⬜🟩🟩
⬜🟩⬜🟩🟩
⬜🟩🟩🟩🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 618 4/6
⬛⬛🟨⬛🟩
⬛🟩🟩⬛🟩
⬛🟩🟩🟩🟩
🟩🟩🟩🟩🟩
Get me coffee and no one gets hurt!
|
|
|
|
|
Wordle 618 5/6
🟨⬛⬛⬛🟩
⬛⬛🟨🟩🟩
⬛🟩⬛🟩🟩
⬛🟩🟩🟩🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 618 5/6
⬜🟩⬜🟩🟩
⬜🟩⬜🟩🟩
⬜🟩⬜🟩🟩
⬜🟩🟩🟩🟩
🟩🟩🟩🟩🟩
process of elimination
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
#Worldle #401 2/6 (100%)
🟩🟩🟩🟨⬜↘️
🟩🟩🟩🟩🟩🎉
https://worldle.teuteuf.fr
Knew right where it was but could recall the name. Africa is crazy that way.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Decided to run code metrics on my current "big" VS project. I felt I had a "huge" code base. My 31K of source code (it felt like more) amounted to little more than 7300 lines of "Executable" code.
Years ago, I scoffed when I read the average programmer writes only about 100 lines of bug-free code per day.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
That code must be well commented to get below a 1:4 ratio!
I was also surprised when I first heard about the 100 lines per day. Actually, I heard it as 50 to 75, which might be even more accurate.
|
|
|
|
|
I know I write more than that.
To err is human. Fortune favors the monsters.
|
|
|
|
|
You are not average or "normal"
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I find that it varies. Application level, more than that. Framework level can be a different story.
|
|
|
|
|
I have a lot of (UWP) XAML; perhaps 25-35%. And don't know if it's considered "executable code" since it's (mostly) declarative; same with simpler properties.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
My ratio is closer to 1:2
102,436 Lines of Code
60,570 Lines of Executable
Accordingly to Visual Studio Metrics.
Some day I have written much more than 100 lines/day of code. Actually close to 1000
|
|
|
|
|
The metric is for released code, meaning that it has been thoroughly tested and integrated.
|
|
|
|
|
"Lines" is not
a valid metric for
modern languages.
|
|
|
|
|
I would not say it is an invalid metric.
It's just not an accurate metric.
Define modern languages.
I can easily write way more than 100 lines of bug free C code a day when deep into a project.
My last project was 1.2 megabytes of source code, not including libraries.
Not sure how many lines.
Maybe I am just a wordy programmer.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
jmaida wrote: not an accurate metric.
Counting statements is more worthwhile than counting "lines". And even then, it depends on what one considers to be a "statement".
jmaida wrote: modern languages
Any language which doesn't have a 1:1 relationship between a "line" and a statement.
I suppose that really only assembly code written on cards had this distinction in the first place.
Although "lines" wouldn't apply to card-based systems, but only to VT- and printer-based systems.
Even BASIC (Dartmouth, 1964) focuses on statements rather than lines and "line numbers" are primarily for specifying the order in which the statements are to be executed rather than to define a "line of code". And, of course, more modern implementations of BASIC-type languages don't require line numbers at all.
|
|
|
|
|
agree
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
If ending in a ';' is the end of a statement in C. Then counting these may be more accurate than simple a line of code. Fortran is statement oriented so it has a better 1:1 ratio.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Visual Studio did the "counting".
Quote: Lines of Executable code - Indicates the approximate number of executable code lines or operations. This is a count of number of operations in executable code. This metric is available starting in Visual Studio 2019 version 16.4 and Microsoft.CodeAnalysis.Metrics (2.9.5). The value is typically a close match to the previous metric, Lines of Code, which is the MSIL-instruction-based metric used in legacy mode.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Gerry Schmitz wrote: Visual Studio did the "counting".
That's your problem, right there...
|
|
|
|
|
Agreed.
Here's
five
lines
of
text!
|
|
|
|