A cable coil will lay flat and neat, and stay orderly indefinitely if two conditions are met:
The coil radius is sufficiently large such that there is little to no tendency to unwind.
There is no twist running the length of the cable.
The solution to 1 is simple: just create loops large enough that no energy is stored in the “big spring”.
The solution to 2 is any wrap method which avoids a systematic twist along the cable. If you were an ant walking along the cable, you should find that if you start on the outside surface of the coil, you remain on the outside as you walk the loops.
One method for coiling cables that achieves both goals:
Hold one end of the cable fixed in your off-hand. Let the length of the cable loosely hang such that it may freely rotate. With your dominant hand, slide it down the cable measuring a length which will create a loop large enough that the bend radius doesn’t want to spring back open. Here comes the big trick. As you bring your main hand around to create the loop, use your fingertips and thumb to roll the cable in the direction which eases the twist along the cable. Finish the loop, and repeat until done. The coil should lay flat on a table without wanting to unspool wider, or spring up and launch loops into the air (problem and solution 1 and 2 respectively.)
Practice the finger tip movement. It’s like tying shoes or whistling. Once you get it, you get it.
Also have one end of the cable loose, and push the tension towards that loose end as you coil, unwinding that excess tangle as you go. Coil the cable in the direction in naturally wants to go after this tension has left and it’s no longer fighting you.
I used to shoot live TV in random beaches around the world and this method worked great every time we packed down. We had coil sizes roughly the length of our forearm for super long cables.
This is essentially the over-under method. The idea is that you do a twist in one direction as you make your first loop, then a counter-twist in the other direction, which causes the second loop to sit “under” itself. So your coils follow a pattern of one regular “over” twist, then a reversed “under” twist. So the net result when you uncoil the cable is zero twists, (or at most one twist in the entire length of the cable, if you started and ended the coil with an over twist.)
Professionals use this for coiling, because it helps with cable longevity and running. Your cables never develop the dreaded twists in the first place, because you’ve never introduced more than one twist into them. And in a 50’ run, one twist is negligible and will work itself out as you coil the cable again at the end of the night.
And a figure-8 coil is basically the same thing as over-under, but laid out flat. This is handy for thicker cables that you coil in place. Hubbell Cam feeder cables, for instance. Each cable is as thick as a quarter, and there are up to five of them in a bundle. So it’s incredibly heavy and hard to work with. Instead of dragging the cable to you, you usually have a crew coil it directly onto a cart or into a case. So you’re wheeling the coil around, following the path of the cables, rather than trying to drag the cables to you. But this means you need a way to coil it flat, and a figure-8 solves this. It achieves the same twist-counter twist pattern in a much flatter (but wider) footprint.
The downside to the over-under method is that if one end of the cable gets pulled through the loop, you end up with a series of overhand knots in your cable, spaced evenly across the entire run. That’s why professionals will use velcro cable ties on all of their cables, to ensure the cable ends stay on the correct side of the coil and don’t get pulled through.
Source: I’m an audio technician. In a single shift, I’ll coil anywhere from 500’ to 2500’ of audio cable. Every mic you see on stage probably has either a 25’ or 50’ cable on it, and all of those need to be packed up at the end of the show. On a big gig, I can easily coil half a mile of cable throughout the day. I always joke that the actual show is only 10% of the job. The other 90% is cable management.
Sounds awfully familiar. One of our customer wanted a very specific option our system does not provide - because it makes no sense at all. But instead that the customer discusses what is good and what is not, based on our >40 years of international experience in the field, we just got a bunch of drawings telling me that I should do something in the way a political committee with no professional input had decided.
Customer pays for it, customer gets it. Fun fact: I know they will get sick of what they cooked up in no time, so I already installed a “kill switch”. As soon as they get sick of their stupid idea, I can reverse it with a single option. Bossman says to take the same amount of money for switching it back, and he knows they will pay.
Anything running on your computer can be cracked; that’s simply the nature of being in control of your device. (Web) Apps where the important stuff runs on a server can’t be cracked because there isn’t any DRM in the first place.
As personal, individual user, who gives a shit? I’ll just wait until a large enough gap between my version and the current version is there to warrent getting a more updated cracked version
I used an outdated version of photoshop for years.
If you NEED regular maintenance builds, it’s probably for enterprise, in which case you open yourself up to a whole lot of legal bullshit by making money using pirated software in the first place.
Much like the old internet adage: if you want to know the answer to something, confidently state the wrong answer, and inevitably someone who knows the correct answer will chime in to correct you.
You used to be able to get people to quickly give you an exact no bullshit straight to the point answer in Linux support forums by making a post along the lines of “Linux sucks because x never works. Windows is obviously superior because it’s possible to make x work”. Someone would then refute all your points and post how to fix your problem.
Counterpoint: devs frequently downplay user’s needs and inflate the importance of their own ideas, and because they’re often in an echo chamber of their own team’s environment, they never hear meaningful kickback from anyone they respect (because they certainly don’t respect users).
Then they share this comic back forth literally every time users complain.
Someone, in the slack channels of reddit’s devs, shared this exact comic with this exact attitude because of the backlash. And it was met with the same approval as the comments here.
Wh have met with the users who use our product. But they don’t seem very able to articulate what it is they actually want or need from the system. It’s always vague ideas and nothing actionable.
Them: Oh we need to be able to find customers even if they can’t remember their account number.
Us: Yes but you can, just enter the company name.
This is usually met with either a vague “yeah” or “no not like that”, and then they never elaborate.
If you make 1x1 pixel transparent undocumented button hidden in the most obscure place, which when pressed will spawn five elephants with severe diarrhea right near the user and then four clowns will appear and rape that user and then a meteor will fall right from the skies, someone surely will build a business process around that button
xkcd
Hot