You mean I’ll de emphasise my quads even further presumably? I tried shrimp squats today and couldn’t do a single one 
Would you program box squats any differently from normal squats? Should I avoid “sit back/use hamstrings” and instead focus on simultaneous breaking of hip and knee?
Guinea!
I wouldn’t really program them differently but be warned if you want to go over 6 reps. Definitely no rocking back!!
What I did coming off an injury was start with a rather high box and push the hips back far, keep shins nearly vertical and use a slightly wider stance. Once I adjusted to that and knew how tp properly load my hips, I lowered the box and broke at the knees and hips simultaneously with my regular stance, basically performaning a regular squat to a box. This makes the squat a lot harder but it’s worth it. I supplement this with lots of front squats (one phase paused and then regular) and a ton of single leg work.
You don’t need to do all of that obv., I just wanted to lay out what worked for me in order to “understand” squats better.
This man was a great guidance counsellor for my rehab and especially my squats and box squats: @FlatsFarmer along with Mark.
This is how I do box squats as well. I actually really like them this way, and I really hate squatting haha. I touch the box pretty lightly too.
so, over the summer I decided to learn python and how to use django. I am very interested in real-time applications, particularly the websocket technology, so I instantly started working on a project with django channels.
I made a chat application first.
There is not much to say about it: features include public and private messaging, attachments, message formatting, moderation (kick/ban/mute) tools, invisible mode, theme and language selection, and tag notifications.
Here’s a feature tour page (the graphical interface looks different as I updated it since creating the page): https://samul-1.github.io/chat1/
Last week, I decided to make an app for playing a card game. This game (don’t know if it’s a thing worldwide) is called dubito, which means I doubt, in Italian.
Here’s how it goes: you have n players, and the deck(s) of cards is divided and dealt equally between those players. There are no cards left. The first player declares a card, and puts down one or more cards covered. All the other players have to put down one or more cards too, when it’s their turn, and they have to be the initially announced card. Here’s the catch: you can lie. You can say you’re putting down 2 aces but it might be a 3 and a K.
At any time, a player can doubt, and the last cards that were put down by the last player are uncovered. If they lied, they take all the cards that were previously put down. If they hadn’t lied, the player who lies is the one who takes all the cards in their hand. To win the game, you must be left with no cards.
A round could go like this:
first player: “3 aces” (puts down 3 aces)
next player: “1 ace” (actually puts down a Q)
next player: “2 aces” (puts down 2 aces)
next player: Dubito! (cards are uncovered, the previous player had actually put down aces, so the last player takes all the 6 cards)
Here’s the code:
I feel like my server-side logic is solid, and it works flawlessly. The frontend js is a hot mess. I am almost embarrassed. I realized I need to learn vue: I would be able to do these things writing one third of the code I did.
Lastly, I made a js-only app which is an assembly interpreter.
https://samul-1.github.io/asm/
It’s not perfect but it does its job well. The type of asm it interprets is the (virtually useless) D-RISC version. There’s an instruction set modal that shows all the supported instructions so you can play around with it. I am aware the way I implemented it is not how you write an interpreter, for the most part. This was more for fun than anything else. Turned out well, for the purpose of playing with code.
Bonus:
http://playcards.altervista.org
Last week I also made this php&ajax app in 48 hours. It’s a much simpler card game than dubito, in which you try to get a score of 7 and a half without exceeding it by drawing cards. I am planning on writing an AI-ish algorithm to allow players to play against a computer, rather than another human.
Maybe you can clarify something for me because today I had a complete black-out with regards to bracing so I googled and found conflicting info. Contract abs and breathe into the contracted abs or the other way around (big breath, then contract abs). I found proponents of both and was like
Press X to confuse
I’ll have a look at the backend bits tomorrow. I don’t know any Vue. Thank you
Big breath and then contract abs - use the air to create tension into you belt
No pun intended
Thanks. Can’t believe I forgot something so fundamental 
This is the funniest thing to me at the moment
Eh it happens. The longer I do this, the less I think about how I do things. One part is experience and trusting your body, the other is a conscious decision because it is deteriating to me if I overthink stuff. One or two cues if I want to improve on something and that’s it.
hey man, what’s going on? I haven’t followed any logs lately (or much of the forums for that matter) so I might not be up to date
I just meant the “bits” pun. Or, what do you mean? 
oh I might have misunderstood your statement “this is the funniest thing to me.” I thought you meant that was all there is to be laughed about at the moment
I highly recommend “Two scoops of Django” if you haven’t already encountered it
I haven’t. I’ll check it out.
No no, I just meant that in the moment I found it beyond hilarious
as a side note, this week we started classes and one of the courses I’m currently following is “programming 2.” the main topic of the course is oop and specifically java. our teacher sucks at teaching, it’s hard to even listen to her for more than 20 minutes straight, so I got a java book and I started reading it by myself. contrarily to what I was expecting, I’m finding it very uninteresting.
it might be because I have just done some reading, no coding yet, and the book starts from the very basics which I’m well beyond. maybe by the time I get to work on some actual code, the boredom will go away. I’m just very much into django at the time, and find java to be an outdated, hardly applicable to real-life situations language. I’m just not that motivated.
also, I’m trying to find an idea for a websocket based app that I might work on next. nothing has come to my mind yet, so any suggestions are welcome.
Good. I started to look a little but it’s not conducive to winding down so I’ll leave your code base until later but first reactions are “write tests”.
Second reaction is refactor a bit. How much? That’s a question of taste. You’ll find you’ll have a period where you overdo it, but eventually settle in to a sweet spot but it’s probably paramount to be overzealous about it for a while to figure out when it makes sense.
For instance, views.py
def chatroom(request, invisible=False):
Go through it and think what are the cohesive units? What comments can be replaced by code? What comments offer no value? (hint: instantiation comments)
Here’s an example
# set user as online
this_user = Profile.objects.get(of_user=request.user)
this_user.is_online = True
this_user.save()
That’s easily a function
def set_user_as_online(target_user):
user = Profile.objects.get(of_user=target_user)
user.is_online = True
user.save()
return user
We return the user for testing purposes primarily.