|
Wordle 1,061 4/6*
⬛⬛⬛🟨⬛
🟨⬛⬛🟨🟨
⬛🟩🟩🟩🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
So, I pay all my utilities via credit card, and I receive emails when the bill is due and amount. Last month, the water department notified me that my bill was $240 and change. Considering my normal bill is $39 my attention was captured.
Here's the interesting thing - about 4 months ago, the water department started rolling out smart meters that they could query and collect usage information. Think now - water department, smart meters, automatic billing.... most of the people I've met from the county departments leave me less than inspired. This month, my water usage has been at a square wave. Normally 400 gallons a month, it's been spiking at various times and days to over a thousand gallons per day. I've already pointed out that their data is corrupt, but all I get is a tired voice on the line.
I may have found a new career, no, sorry misspoke, consulting opportunity.
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.
|
|
|
|
|
charlieg wrote: consulting opportunity
Working for them seems more of a headache opportunity.
"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
|
|
|
|
|
charlieg wrote: over a thousand gallons per day.
Wow! That's like a 1" pipe going full tilt the whole day! Maybe you shouldn't fill your pool daily; you know, it's not a bathtub 
Mircea
|
|
|
|
|
|
Whilst I was perusing another article in the MSN info world (that another member had mentioned) I stumbled across the following article "Scientists have found 'evidence' of advanced alien civilisations". The article relates to a scientific study of a combination of star surveys (roughly 5 million stars) and a methodology to filter the stars looking for specific emission markers that make the star unusual and possibly a Dyson sphere under construction. In the article there is a link to the official paper that the group produced (haven't finished reading it yet).
My own feelings are that Dyson spheres sound cool, but the amount of physical material that would go into making one would be prohibitive. Stars are big. Even red dwarf stars. Surrounding the star with technological material (all of the support devices to convert, control the flow of energy, store and forward it to the area of need). Would require the literal conversion of several star systems of every bit of matter in them (planets, moons, asteroids, every spec of material left over from the star formation) to provide the raw materials for the build. We might want to look for star systems surrounding a suspected Dyson sphere that have no planetary bodies associated with the star.
Of course, an advanced civilization might be able to capture the solar wind and also convert a large part of the radiant energy directly to usable matter.
In any case, here is the link. Have fun.
MSN[^]
|
|
|
|
|
I suppose one way to do it is to cannibalize the other planets in the system. Like hit each planet with a giant spatula to flatten it.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Here's a question, how do you maintain gravity in a Dyson Sphere (assuming you do not have "artificial gravity")?
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
I would suggest spinning it. You'd wind up with only a ring world's amount of living space but (like 640kb) that should be enough for anyone. It would probably make for an interesting typography in that "down" might not be perpendicular to the surface, but hey, you've already solved the hard problem of making and spinning it. This is probably a minor issue, comparatively. On the plus side there's no need to worry about artificial gravity failures sending the atmosphere and other loose material, like people, into the sun.
The "unused" sides, the axis poles as it were, could be for energy harvesting and such. They'd also make fairly good access points for ingress/egress of the sphere.
|
|
|
|
|
From the CP newsletter
Astronomers are on the Hunt for Dyson Spheres - Universe Today[^]
Gary Stachelski 2021 wrote: but the amount of physical material that would go into making one would be prohibitive
There are all sorts of engineering problems, economical problems, and political ones as well. Those are pretty standard constraints on all fantastical theoretical constructs. Even much smaller ones.
Consider this - lets say one claims that the material in the solar system is enough. How do you dismantle Jupiter without destabilizing the entire star system.
Or what political system must the world have in place such that it would remain stable enough for perhaps hundreds of thousands of years while this was happening.
Those who want to believe often rely on yet more fantastical stuff to avoid such problems.
|
|
|
|
|
|
Startups will claim anything...
Hogan
|
|
|
|
|
The problem and solution reminds me of analog computing but using light instead of electricity.
Interesting that both quantum and this light method both look for minimal energy states to define the best possible solution to the problem.
|
|
|
|
|
I've come to understand quantum computing to be a bit like Plinko on the Price is Right.
You set up your equation which can metaphorically be represented as placing the pegs into the board and then setting all the dividers for the troughs the chip may eventually fall into.
As a chip dropped in plinko settles to the lowest entropy of a trough. "Execute" is dropping a bunch of chips into the board and letting them settle entropically, then your answer is in counting the troughs.
There are some ways this metaphor doesn't play but some ways it plays really well.
|
|
|
|
|
John F. Woods once said : “Always code as if the person who ends up maintaining your code will be a violent psychopath who knows where you live.”.
There should be a similar saying in regards to writing (non unit) test cases.
"Always write test cases as if the person who ends up testing your software is a 5 years old without any knowledge of the software"
I'm going through some test cases on a large software and the tests cases are just a description of what I need to do.
In reality, I have to do about 20 different steps to get there and go through thousands of records (SQL) to find one record that will work.
Seriously, do you know of any good white paper on how to write good test cases ?
groan.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
Maximilien wrote: John F. Woods once said : “Always code as if the person who ends up maintaining your code will be a violent psychopath who knows where you live.”.
This... this right here... is gold. 
Maximilien wrote: In reality, I have to do about 20 different steps to get there and go through thousands of records (SQL) to find one record that will work.
Sounds like someone who wrote those tests didn't know squat about writing tests (which is a lot of people). A unit test should never connect to a live resource. Not only is that non-deterministic, but you can't run 1,000s of tests quickly that way.
Maximilien wrote: Seriously, do you know of any good white paper on how to write good test cases ?
Wish I could help with that buddy. For me, it was a combo of coworkers helping and trial and error with Stack Overflow Googling.
Jeremy Falcon
|
|
|
|
|
we're not running unit tests; I don't know how I could integrate that in our ancient/antiquated codebase 
We're doing functional and integration testing and acceptance testing.
It's just hard to change the inertia; that's why I would need some good resources to help me suggest some changes.
Thanks for the moral support.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
Ooops. Totally missed the non-unit part. 
If these are integration "test cases" they sound more like documentation for manual steps than anything else then. Probably could've achieved the same thing in a README.
Jeremy Falcon
|
|
|
|
|
Would test automation help?
Had used Selenium framework, for a web application, some years ago, and our test scripts automated all the steps. There must be a similar framework for desktop apps.
|
|
|
|
|
My Sr. partner is the best when it comes to breaking things:
0: Entering non-numeric chars where numbers should go or invalid numbers such as 1,1.2 or 1.1,2 (fun fact, letters up to f will happily identify as numeric)
1: Extremely long text/numbers, special characters, 0s as divisors
2: Leaving 'required' fields blank
3: Using the back button in web apps
Of course, there are some situations you can't predict. That's what users are for!
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
and/or
- cancel dialogs
- close app (with click on "X") while db is in edit mode
- kill app with task manager while someone is editing something
- use special - non ascii - chars where it is not expected
- simulate high load with endless read/write operations
- change screen size/resolution to unusual values
modified 5hrs ago.
|
|
|
|
|
It comes down to my biggest beef with tests and that's being only as good, generally, as whoever wrote what they're testing.
For one, some jabroni didn't really write tests for your system. They wrote some documentation.
If you can't run them in an automated fashion - without manually hunting records down and manipulating data? Then they simply aren't tests and if the person's task was to write tests, they 100% failed that task.
You write the test so that it stages the data you know will work and then delete that data post-test.
[OneTimeSetup] / [OneTimeTearDown] are the decorators for NUnit to do stuff like that.
When we started writing a bunch of tests, we settled structuring things linearly like the following with regions for:
Class Members
Assemble/Setup
Act/Invoke
Test Asserts
Cleanup
|
|
|
|
|
Get some experienced testers to bash it hard - much better than test scripts IMHO - writing(and testing / maintaining test scripts) is often harder than coding the application
In a closed society where everybody's guilty, the only crime is getting caught. In a world of thieves, the only final sin is stupidity. - Hunter S Thompson - RIP
|
|
|
|
|
It seems like you're suggesting that getting experienced testers to thoroughly test a product is more effective than relying solely on test scripts. This approach can indeed provide valuable insights and uncover issues that might not be caught through automated testing alone. Your quote by Hunter S. Thompson highlights the importance of thoroughness and vigilance in testing to avoid pitfalls.
|
|
|
|
|
Wordle 1,060 4/6
🟨⬜🟩⬜⬜
⬜⬜🟩🟩⬜
⬜⬜🟩🟩⬜
🟩🟩🟩🟩🟩
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
