The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
1. The lounge is for the CodeProject community to discuss things of interest to the community, and as a place for the whole community to participate. It is, first and foremost, a respectful meeting and discussion area for those wishing to discuss the life of a Software developer.
The #1 rule is: Be respectful of others, of the site, and of the community as a whole.
2. Technical discussions are welcome, but if you need specific programming question answered please use Quick Answers[^], or to discussion your programming problem in depth use the programming forums[^]. We encourage technical discussion, but this is a general discussion forum, not a programming Q&A forum. Posts will be moved or deleted if they fit better elsewhere.
4. No politics (including enviro-politics[^]), no sex, no religion. This is a community for software development. There are plenty of other sites that are far more appropriate for these discussions.
5. Nothing Not Safe For Work, nothing you would not want your wife/husband, your girlfriend/boyfriend, your mother or your kid sister seeing on your screen.
6. Any personal attacks, any spam, any advertising, any trolling, or any abuse of the rules will result in your account being removed.
7. Not everyone's first language is English. Be understanding.
Please respect the community and respect each other. We are of many cultures so remember that. Don't assume others understand you are joking, don't belittle anyone for taking offense or being thin skinned.
We are a community for software developers. Leave the egos at the door.
Maybe this is something well known, and I'm just late to the game: If you have a cordless tool, you are likely on a forced replacement scheme, and you don't know it. About 10 years ago I bought a cordless hedge trimmer, and its worked well. In the winter I bring it inside and store it, battery out, in the basement where it keeps relatively nice and warm. This year, after recharging the battery overnight, I went out yesterday to trim the hedge. The battery (NiCad) ran down after about 5 minutes, so I'm guessing its just not holding a charge any longer. No problem, I'll just go to the vendor, a national chain, and get a new battery, right? Um, no. That particular battery is no longer available. And so far, I've been unable to locate a third party replacement part.
It looks like the battery pack is screwed together, so maybe I can take it apart, and replace the individual cells. Maybe. Its probably soldered together, and I'm not sure I'd trust my soldering skills if I have to solder directly to the replacement cells, if I can even find something suitable.
So, in all likelihood, I'm going to have to bin an otherwise perfectly good hedge trimmer, just because I can't replace the battery pack. That's just wasteful. Not to mention an added cost. I do have an old pair of hedge trimming shears, and I used them to finish the job. Maybe I'll just stick with them. But if I replace the electric trimmer, I'll definitely consider a corded trimmer rather than cordless.
So if you have cordless tools that are a few years old, it might be worth buying a spare battery pack, or two, for the future.
The mention of computer history and the book, "Soul of a New Machine" made me remember the old days and mini-computers. They were called "mini" because they weren't like the old room-filling mainframes. Most of these were about the size of standard refrigerator. That's the era in computing that I am most fascinated with and one that the details of are mostly unknown to most people today. I especially like how the machines were built. They used what is known as the "bit-slice" design. The CPU usually took an entire two-foot square circuit board and it was built with circuits that were initially just one bit wide and they essentially stacked them together to achieve the word width they wanted. Many of which were 32-bits and, as I recall, DG's was 36. AMD was probably the biggest company making the chips at the time and eventually they came up with 4-bit wide chips. All of this was before microprocessors became useful enough to compete with the bit-slice designs.
An amusing story from the tail end of this era : I worked at a company that had a room full of mini-computers including several VAXes. We were doing a project that controlled the North Shore Pipeline and talked to several RTUs using the Modbus binary protocol. It uses CRC-32 to compute a checksum for every packet and that would bring the VAX 750s to its knees. The CPU usage would spike every time because this was before the table-driven algorithm had been publicized. DEC's answer was to implement the CRC-32 algorithm in firmware. To implement this a new set of microcode on EPROM was installed and the CPU board was re-wired. The local service guy, Ed, came and had to change the wiring on the CPU board which was ALL wire-wrapped. I couldn't believe it. It was NOT a printed circuit board - it was all wire-wrapped. Those modifications made a huge difference and CPU usage was normal afterward. This was in around 1985 or so and it still amazes me.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
"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!
"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
Shell and hotkeys became unresponsive after awhile of using it. Couldn't control alt delete. Had to hit the "Oh Elephant!" Button.
Browser pages becoming unresponsive and I'm on a Ryzen 7 32GB RAM @ 700MBits of pipe.
So it might be a networking issue. I've had problems with them hosing my drivers already this year, and it has been awhile since i've seen this but in prior windows when you had hangs deep in the network stack the whole system would crawl even if you didn't think you were doing much networking, mostly because of the timeouts on things like background UPNP and SMB pinging
I just have to hit alt-ctrl-del to make the login button appear (instead of it being visible right away after restart by moving the mouse), but apart from that, it works. I have not restarted a second time though.
The news item posted by Kent today about a new "PriorityQueue" feature in NET 6 [^] triggered an itch i call: "i-could-make-one-of-those."
Since I had never experimented with SortedSet, I decided to use that and see where it took me. And, it took me to an interesting place as i wrestled with how to define a generic wrapper structure ... SortedSet<T> requires a Type with an IComparer implementation.
After muddling around for an hour or so (several mental buffers needed refreshing), i had a working example that i then tested.
And, then i got snagged as i changed a value in a SortedSet element ... a DateTime Property ... and it appeared the Set did not sort as expected.
With growing frustration, I tried different values, and re-tested.
i began to get angry as my cherished image of myself as an expert debugger began to resemble the aging wreck i see in any mirror i am unlucky enough to look into by accident
Finally, it dawned on me: i expected the wrong result ! Yes, the beast was doing what i told it to do.
i think we need a new word for this special kind of bruised-ego chagrin mixed with plummeting self-esteem ... i'll try to think of one, later ... first, I need to go outside and scream some more.
p.s. code on request
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali