|
I learned something new here today!
|
|
|
|
|
Then my job is done. Cocktail time!
(Does it count if I also only learned it today?)
TTFN - Kent
|
|
|
|
|
Hey, by any measure that's pretty sharp!
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
pfff... where is the innovation in that?[^]  
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.
|
|
|
|
|
And it's whispered that soon
if we all call the tune
Then the piper will lead us to reason.
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
That's not a flute, that's a implement that every small child in the West gets to torture their parents with as they grow up... otherwise known as a... recorder!😱
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
That was my reaction as well, but it seems a recorder is actually a type of flute:
Quote: The recorder is a family of woodwind musical instruments in the group known as internal duct flutes: flutes with a whistle mouthpiece, also known as fipple flutes.
TTFN - Kent
|
|
|
|
|
If you have never heard 25 third-graders playing their recorders together, you are lacking the background to understand the comment by GuyThiebaut about the recorder being an implement to torture the listener.
Hint: The exact pitch is very dependent on how you blow it; you can pull it up and down by at least a quarter-step by blowing differently. Don't expect those 25 recorders to be tuned to each other initially, but that really makes no difference anyway when third-graders are blowing them. Played by professional musicians, the recorder is a beautiful instrument. As the first instrument, made mandatory for all grade school kids to learn in Norwegian schools in my childhood, it is the worst possible choice. Even worse than then violin as a first instrument - violin starters can at least play four notes in tune, on open strings.
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
Maybe offtracking slightly, but I'll risk it: Every flute lover will also love Erik The Flutemaker: The Spiel[^]
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
C# 12 as part of .NET 8 introduced a compelling set of new features! In this post, we explore one of these features, specifically primary constructors, explaining its usage and relevance. "There can be only one"
|
|
|
|
|
If it ain't broke, don't fix it! 
I often roll my eyes at all these new language features and static analyzers that complain when a 10-year-old code base isn't using them.
|
|
|
|
|
For it to be a meme to judge programming by lines of code, the big dogs expend a great deal of effort to reduce lines.
Too much of this gatekeeping guardian elitism babysitting.
Let's take our super flexible blank books and just go ahead and insist that random pages of it have to contain certain plot points to make sure the author doesn't mess up the storytelling.
|
|
|
|
|
If you are measuring productivity by counting LOC, then these new tool are counter-productive.
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
Kent Sharkey wrote: "There can be only one"
Use Singleton 
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.
|
|
|
|
|
Microsoft claims the latest incarnation of its lightweight Phi-3 Mini AI model rivals competitors such as GPT-3.5 while being small enough to be deployed on a phone. Is that an AI in your pocket, or are you just thinking hard?
|
|
|
|
|
The irony is lost on few, as a Chinese threat actor used eight MITRE techniques to breach MITRE itself — including exploiting the Ivanti bugs that attackers have been swarming on for months. They forgot to read their own reports
|
|
|
|
|
Kent Sharkey wrote: They forgot to read their own reports
Like many police officers, politicians, religion speakers: "Do as I say, not as I do"
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.
|
|
|
|
|
Jesus wrote (Matthew 23:3): So you must be careful to do everything they tell you.
But do not do what they do, for they do not practice what they preach.
For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life.(John 3:16) ![Badger | [badger,badger,badger,badger...]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/badger.gif)
|
|
|
|
|
You can plan, strategize, chunk, fold, spindle, and mutilate a project for countless person-hours, and you still won’t know the difficulties that lay ahead in actually writing the code. Because we suck at defining projects
|
|
|
|
|
I'm pretty good with my estimations and have worked with people who are also pretty good at it. The biggest problem is bosses/management don't want to hear the actual estimate.
Long before Agile and Scrum, Novell adopted the mantra that all projects take two weeks. I was in one meeting where everyone on our team was asked how long it would take to finish--mind you it was just our team--and everyone said "two weeks". I said "five months." I got laid off six weeks later. The project took exactly five months to finish (and still didn't ship for another six months after that.)
|
|
|
|
|
Joe Woodbury wrote: The biggest problem is bosses/management don't want to hear the actual estimate.
100% this!
For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life.(John 3:16)
|
|
|
|
|
amen. This is one of the nuggets that came forth from the original Extreme Programming book. If you aren't doing the work, you don't change the estimate. It's amazing how everyone continues to lie about this. "I'm sorry, I did NOT miss my estimate, I missed yours" was a common theme in so places I worked.
The worst part is that by not accepting the estimates, the company sabotages their own efforts and developers never learn to estimate properly.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
Kent Sharkey wrote: Because wethey (managers, marketing, sells...) suck at defining projects
FTFY
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.
|
|
|
|
|
Kent Sharkey wrote: Because we suck at defining projects
Engineering is usually quite good at estimating the time required for a project. The problem is that Sales always wants it earlier so they can show it at the next expo, and they have the ear of Management.
Given that most companies are profit-driven, the company that delivers first is likely to get the most sales, and that Management is rarely held liable for any failures, there is no real solution to the problem.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Daniel Pfeffer wrote: The problem is that Sales always wants it earlier so they can show it at the next expo
Not only Sales - the customers, too!
In my student days, one large project was implemented using an IBM prototyping system with APL as the prototyping language! It was really great (if you could handle APL...). The guy who introduced the system to us told about one 'problem': Customers testing out the prototype often would say: "That's exactly what we need; we'll take it. You'll receive our payment shortly. Thanks and goodbye!". So the developers must make sure to always leave some essential functionality out, and make that very clear to the customer, to stop him from running off with the prototype. Quite often, the customer had a hard time understanding why it would take another six months to implement the system - they had seen in running perfectly in front of their eyes, why would it take so long?
Not only salesmen but customers crave for news at every expo. I worked in a company where the sales people held back some new developments for expos/releases: As developers, we were eager to display all we had achieved, but the sales people said "No! We have enough news for this time, we'll hold the rest back, in case we don't get around to developing any eye catchers in the next round". We developers were told not to reveal any of the already-implemented functionality (it was not yet linked in the product sold) to customers; that should be a new big headline a few later. You don't gobble all the vitamin pills in the bottle in one go 
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
