And 10 reps is not low reps either. It's on the upper end of what people usually use in their workouts.
40 karma · joined June 1, 2017
And 10 reps is not low reps either. It's on the upper end of what people usually use in their workouts.
Much better to start with a lot more than the minimum so you have a decent safety margin (and lifelong habits that will keep you healthy for as long as possible).
It's a fun sport that keeps you fit but is also very cerebral. In a way it's a lot like playing a computer game where you level up your character. You program yourself to execute certain moves in certain scenarios. I have countless notebooks full of flowcharts and notes. Can highly recommend it.
You can also run/walk in intervals as long as you keep the heart rate up. If you want to get fit, a heart rate monitor is a great investment (something like a polar h10 can pair with your smartphone).
Main lesson is that you should not use it for everything (yes, the books say it, but it's easy to overdo it in the beginning). Don't do DDD for the CRUD parts of your app. It works extremely well for business use cases, but it's very bad at CRUD. A mix of both really hits the sweep spot though.
No microservices though, just a monolith. Imo most businesses shouldn't need microservices, only the ones that really need to scale. We definitely don't have anything even close to that.
Looking forward to the membership part, might use it for another project of mine.
A disproportionate amount of our members [0] are programmers or software engineers.
Remote: Yes
Relocate: No
Technologies: PHP (DDD w/ CQRS/ES), Symfony, React. Interested in Kotlin, maybe Java or C#.
Resume: Wrote a book (Professional PHP). Also see my blog and Github.
Email: firstname@lastname.ch
If you want to build a closed system, it doesn't make sense to put it into a gravity well.
You can also do inverted rows under a table by holding on to an edge (not comfortable, but works).
You could invest into a dumbbell and/or resistance bands and do row variations. Or a TRX for inverted rows.
Or go to a park or anywhere else where you can hang onto to do your pullups.
If you don't have a competition coming up (or if you are just training for health), then a mix between aerobic and anaerobic-alactic (strength, explosiveness) is much better.
Check my website [1] for the training methods that I usually recommend. For a non-athlete or someone in off-season I would stick to cardiac output, threshold training 1x per week and strength training.
You will see much better results and you will sleep better if you change your training approach. Hope that helps :)
[0] See Arthur Lydiard's work
Sidenote: I would recommend actually reading the tabata study. You can see that they also plateau'd after a few weeks (but the study duration was not long enough to see the long-term effects).
I wrote my book Professional PHP [0] as a guide like that, but of course it's heavily skewed towards building a PHP webapp (even though most of it is also applicable to other OOP languages).
But to be honest, I wouldn't try to narrow it down to a single book. Start with the classics like clean code, code complete 2, pragmatic programmer and then work yourself towards effective java, implementing domain driven design etc. I have a list of my recommendations published here [1].
It was a little work to set up the workflow with scripts etc, but being able to write the book in markdown and still having full control over the design was definitely worth it.
[0] sample here: https://patricklouys.com/professional-php-sample.pdf
For large projects, I strongly prefer a frameworkless approach. If you do throwaway apps for an agency, then a framework is probably the better choice.
That being said, I am still forced to use Symfony at my current job. It only gets in the way sometimes, it's not too bad.
On my previous job we went from CodeIgniter to frameworkless and I really liked that. Not having framework constraints working against you was really enjoyable to work with.
In both cases management was on board with scrum and knew what that meant. Everything was estimated by devs, not managers. If there was an external deadline, scope was adjusted to meet it.
No comparisons to time or between team members are made. I think that's really important. Management is on board with that. If it wasn't, it probably wouldn't work.
- Sapiens: A Brief History of Humankind
- Never Split the Difference: Negotiating As If Your Life Depended On It
- Tools of Titans (was positively surprised by this one)
For developers I can highly recommend the Domain Driven Design books by Vaughn Vernon.
I think it's a little more to the point compared to Extreme Ownership.
Professional PHP: Building maintainable and secure applications