Handcuffs out of a belt: Making handcuffs out of a belt is a good way to make a living. It’s not just for policemen or leather enthusiasts. Making handcuffs out of a belt is a great way to make money, too.
This short video shows you how to do it.
The buckle of the Handcuffs out of a belt is generally one inch wide, so that should be the size of your handcuffs
Chastity belts are the most visible and most symbolically important piece of personal protection equipment. However, they are rarely used. In fact, the vast majority of people who consider themselves “perverts” or “people who get off on things” don’t wear one for fear of being seen (and possibly arrested). And as a result, there is a lot of stigma attached to wearing this kind of thing.
We see this everyday in our office and at home:
- My boss uses it when he goes out drinking; he wears it so that people don’t know he drinks (he doesn’t have any sensitivity issues or anything).
- My 16-year-old son has one so that his girlfriend can show him how to use handcuffs; she was afraid that if she showed him how to use them, he might try to use them on her someday.
It turns out there is a lot more than just practical reasons why people choose to keep their genitals in their pants. If you want to learn more about this subject, check out the rest of this article!
a belt can be used to make handcuffs because belts don’t break easily and it’s pretty hard to get out of them once you tie your hands together with them
I’m a big advocate of working from both ends in defining your product. You need to understand what your product is and how it solves a problem (the question is, why does it solve that problem?); and you also need to understand the pain points people have and be able to address them.
It needs to be a continuous process, not just one time event. And when that happens, you are on the right track.
The advantage of the “work-from-both-ends” approach: it’s both fun and productive (and sort of kind of not). It allows you to improve your understanding of the problems people are experiencing and their motivation for using your service (and sometimes this knowledge can lead you down an interesting or novel path). It also allows you to test out new ideas, which can make all the difference in making great products.
The disadvantage of thinking about it as “two distinct phases”: sometimes these two phases overlap, so it’s easy to end up with a product that doesn’t solve what you think it can (or vice versa). It also means that when things don’t work out as planned, you have been doing the wrong thing all along.
In general though, I think this approach works pretty well for startups; if you give yourself enough time without getting bogged down in perfectionism; if you have a little bit of outside support from investors like Andreessen Horowitz; if you give yourself a bit more room for experimentation; and if your team is motivated by success rather than failure (which probably means having more owners than employees), I would recommend this approach as a good one for startups (this comes at no cost to my investment).
if you are planning on
What are you doing?
I was recently asked by an engineer who had just created a new app to help him and his team manage the bugs they were creating. He said he was using the Slack channel there. I got a little confused at first but then remembered that it’s a channel where people talk about their current project and if they want to discuss something they can do so in real-time (without having to ask their teammates for permission). As far as I know, this is totally legal.
But what are you doing? Why are you asking for help? What is the purpose of your use of the Slack channel? Could it be out of spite or malice? Is this just a bit of flakiness or is it really a serious issue? While I would suggest that if you are using Slack just to vent your frustration because someone has said something annoying, then that’s OK, but if you are asking people to help solve your problem, then please stop. You need to be clear with everyone involved before you ask them for help: not only should you be clear about what exactly is needed and why, but also about who will be helping and who will not (e.g., every time someone wants to ask someone else for help, say something like “This is not a request for help from anyone on my team — it’s between me and my teammate — please don’t make any assumptions”).
By the way, this is probably one reason why I don’t use Slack myself: when I was starting out I found that it can be very hard to enforce such rules; sometimes there were some hidden agendas behind someone asking me (which was especially frustrating when there was no obvious way of knowing who actually wanted what). If you want to find out how I enforce those rules at work, check out my blog post on BetterCodeOfTDD.