patricklouys

Using 10lbs for shoulder press does absolutely nothing for your fitness. Even 50lbs barely does anything unless you are completely untrained.

And 10 reps is not low reps either. It's on the upper end of what people usually use in their workouts.

It's not ok to plateau at that level. You will get old, your strength and bone density will go down and it is a lot harder (but still possible) to improve those when you are old.

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).

Brazilian Jiu Jitsu (a large percentage of my training partners happens to be in IT).

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.

Aerobic training is all about the heart rate. You have to get it up to around 120 or higher (and keep it there for a while) to have a training effect. Unless you are REALLY unfit, walking is probably not enough.

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).

Yes, we did all that a few years ago and it's still in use. Clean code, hexagonal architecture, DDD, event sourcing.

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.

Thanks for creating it. I sold the ebook variation of my book through Gumroad and it was a very good experience.

Looking forward to the membership part, might use it for another project of mine.

I liked the beginning of the Three Body Problem, but it got really weird towards the end of the first book. I had already ordered the next 2 books but couldn't motivate myself to keep going. Does it get better?

Brazilian Jiu Jitsu. Problem solving under stress (and will get you fit at the same time).

A disproportionate amount of our members [0] are programmers or software engineers.

[0] http://bjjlab.ch/

Location: Zurich, Switzerland

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: [email protected]

Check out what happened to the Venera landers. It's really hostile at the surface.

From the ground. Building materials etc.

If you want to build a closed system, it doesn't make sense to put it into a gravity well.

But where do you get additional resources?

If your doors are sturdy, make a knot in a towel, hang it over the door and close it. Use that to do pullups. I used to do this a lot during traveling.

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.

Your problem is all the anaerobic-lactic work. Anaerobic-lactic training leads to quick gain over the short-term, but after 3-4 weeks you plateau and from then on you burn out if you keep doing that (This is why most competition preparation programs for endurance athletes only have anaerobic work in the last few weeks before the event). [0]

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

[1] https://fit4bjj.com/

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).

Depends, what kind of application are you trying to build? What programming language?

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].

[0] https://patricklouys.com/professional-php/

[1] https://patricklouys.com/resources/

Mixing Secrets for the Small Studio by Mike Senior is what you are looking for.

I used pandoc to format my book [0]. Not everything worked perfectly, I'm pretty happy with how everything turned out (especially the print version).

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

This is probably bad timing with the Uncle Bob controversy on Twitter recently, but the book is good nonetheless.

There is nothing wrong with using null in PHP...

I feel your pain. That's my biggest gripe with Symfony. Sometimes it feels like I am spending more time configuring that programming.

That's not true. I've worked on large applications with frameworks (CodeIgniter, Symfony) and without frameworks (but with composer packages). In the beginning you might spend a little more time on wiring things together, but on a large enough application your framework will always get in the way somehow and you will have to find workarounds.

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's what an IDE is for. I've been programming PHP for over a decade and since I switched to an IDE this became a non-issue for me.

PHP handles null better than Java. That's the one thing that kept me from switching to Java tbh.

I like to use the same approach, I even wrote a tutorial [0] and a book [1] about it.

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.

[0] https://github.com/PatrickLouys/no-framework-tutorial

[1] https://patricklouys.com/professional-php/

I have used scrum in two completely different companies and it was working really well in both.

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.

Yes, we have been using them successfully for quite a while. We only use it to estimate roughly what fits into a sprint.

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.

- A Guide to the Good Life: The Ancient Art of Stoic Joy

- 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.