|
Yes, in the same vein, I have been boycotting luxury cars and hotels since ever I was born to protest against wealth, and so far I have been able to stick to this commitment.
|
|
|
|
|
|
Watching or participation?
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Actually participation because it is proven, but watching may probably also cause endorphin addiction. And if not coupled with beer and snacks, less dangerous than participation. (I have an interesting theory concerning "no sports lifestyle" which somehow goes minimal loss of life expectancy vs. shorter yet happier life without injuries).
|
|
|
|
|
Breathing.
Whenever you find a way to monetize air I also want a cut.
Wrong is evil and must be defeated. - Jeff Ello
Never stop dreaming - Freddie Kruger
|
|
|
|
|
Food
Water
Oxygen
Carbs
I'm retired. There's a nap for that...
- Harvey
|
|
|
|
|
Survey inquiry point - song heading? (13)
"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!
|
|
|
|
|
No idea about "song heading", but how about
QUESTIONNAIRE
?
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Survey
inquiry QUESTION
point N
song AIR
heading E
QUESTIONNAIRE
You are up tomorrow!
"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!
|
|
|
|
|
N is a point on the compass
AIR is a song
E is a heading (similar to a point on the compass)
I can only figure these out when someone else provides the answer.
|
|
|
|
|
I didn't even get it when the answer was given.
I had to look up what "Air" [^] was in this context.
Quote: An air is a song-like vocal or instrumental composition. The term can also be applied to the interchangeable melodies of folk songs and ballads
It's a good day, I learnt something new.
// TODO: Insert something here
|
|
|
|
|
Youv'e never heard of Air on a G String ?
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
|
|
|
|
|
Nope, turned on safe search filter and looked it up. I've never been into classical music.
// TODO: Insert something here
|
|
|
|
|
I prefer Hair on a G String ...
"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!
|
|
|
|
|
Now now
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
|
|
|
|
|
I used to be a software architect. I think that's part of why I employ such a jaundiced eye when it comes to layered service architectures and sweeping design patterns just because and drowning in UML because reasons.
It's true that when you're dealing with million dollar implementations, multiple deployment points, and disparate teams a lot of this abstraction can be useful.
But how common is that in most people's development? I know it is for some of you, sure, but I think you're in the minority, or at least projects like these are in the minority. Not everyone is Plum Creek or Alcoa.
It seems like the field of software architecture has taken on a life of its own and coupled with CPU cores to waste and infinite scaling out it has - and i'll just say it - poisoned software development.
Just because you know how to do something doesn't mean you should. Most software application architectures do not survive contact with clients plus the erosion of time. They have a shelf life of significantly less than 10 years without some major portion of them being retooled. There are exceptions to this, but designing every solution to be that exception is a waste of time, money and creative energy.
I'm also going to come out and say it makes things harder to maintain. When you're working with 20 different classes and interfaces where 3 would do it just increases the learning curve. There are definitely diminishing returns when it comes to decoupling software from itself, and you run into the cost/benefit wall pretty fast. It can only take you so far. It's best not to overdo it.
Every fancy little UML entity you drop into your project increases the cognitive load of your project for other developers.
Personally, I wouldn't care about that, because "cognitive load" is fun as far as I'm concerned but most people just want to do their work and go home, not spend odd hours studying someone else's work just so they can use it.
Keep It Simple Stupid.
Whatever happened to that?
Real programmers use butterflies
|
|
|
|
|
Good point, I'm not unfamiliar with UML, in our shop it was all done years ago and luckily I did not have to redesign any parts I'm working on.
Sometimes when I see articles on CodeProject about architecture I wonder if the person who wrote it was bored and had nothing better to do than writing lengthy theoretical and incomprehensible articles.
|
|
|
|
|
Yes to this. Glad I have some support here. Everyone but you and Sander are all sideeying me now.
Real programmers use butterflies
|
|
|
|
|
|
honey the codewitch wrote: Everyone but you and Sander are all sideeying me now.
Nah we're not. I've thought similarly for a while now.
Sticky-tape solutions are appropriate in all sorts of places.
Slapping a newsletter on the fridge? Sticky-tape.
Putting up a car-port? Bolts.
How much of the world does it
Slapping a newsletter on the fridge? Measure the thickness of the door's steel, weigh the newsletter, calculate load-bearing ability of door skin, add reinforcement to handle larger photos in the future, drill and countersink holes, punch holes in corner of picture, use supplied allen-key to fasten bolts that secure the pic.
|
|
|
|
|
Absolutely sensible.
Real programmers use butterflies
|
|
|
|
|
honey the codewitch wrote: not spend odd hours studying someone else's work just so they can use it.
Most don't bother with the "understanding" bit at all: Stack Overflow Patchwork | CommitStrip[^]
Go to QA and look at how many people want code converted from C++ to Python (or vice versa) so tehy can hand it in, or want trivial code explained to them.
"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!
|
|
|
|
|
|
Most of my code goes directly into (ASP.NET Core) Controllers and PageModels nowadays.
I have a Core project, which has code shared between all my projects and a SqlServer project for my database stuff.
Then a Services project which has some common services, like Smtp, some Azure stuff, etc.
All injected using the default .NET Core DI library.
Sometimes I think, maybe I'll need this piece of code in another page later on, but then I ignore that thought.
When (if) I actually need to re-use that code it's just a minor refactoring to move it to the Core, SqlServer or Services project.
I recently made some NuGet packages for functions I use over and over in different projects.
I'm also not concerned with keeping my copy/pasted functions up-to-date in every project anymore.
It works in older projects in its current state, so no need to "fix" what isn't broken there.
And that's how I roll nowadays, KISS and YAGNI
|
|
|
|
|
It sounds like you've got a good handle on things.
Real programmers use butterflies
|
|
|
|