German Gonzalez-Morris

Hello,

Looking at the index, I can see more references to AWS EKS than a native Kubernetes approach. Maybe the book handles k8s transversal, and EKS is a simple example?

Regards,

German

Welcome & Hello,

Regarding OAuth2, which flows do you cover in the book?

Maybe the most popular(s)?

(i.e.: Authorization Code Flow)


Regards,

Germán

Campbell Ritchie wrote:I think I have mentioned this here earlier this week, but do you really want speed reading? Are you risking missing something, particularly if natural language text has more redundancy allowing readers to understand it more easily?

Yes, I know it is not the best practice, however under certain circumstances, the workload is more significant than expected, and speed reading could be a workaround.

And that's the core of my question. Do you have any successful experience with it?

Felienne Hermans wrote:Do you mean speed reading of code or of text?

reading code (that may have a relationship reading text?)

Hi Felienne,

It is understandable to find cognitive topics in the book's index, and the titles make sense. Do you have any personal (or third party) about improving speed reading? (li.e.: improving pull request analysis, or any other skill).

Regards,

German

Hello Mohamed,

How do you handle cloud-native services (for example) to AWS services, such as S3, DynamoDB, Step Functions?

Perhaps, there is a mapping among Native service (repository, ETL, etc.) and proprietary Cloud Platform.

Regards,

German

Hello Yehonathan,

This  is an interesting paradigm, in particular starting from separations of code from data, nevertheless, I wonder about "Control concurrency in highly scalable systems."

Does this approach also is based on immutability, or there are other aspects to achieve that control?

(perhaps eventually consistency?)


Regards,

German

Hello Daniel,

This looks like a cool book from basic to advanced topics.

It paid attention about Memoization from TOC.

How deep do you go into Memoization ?

Regards,

German

Hello & Welcome,

Is The Career Toolkit targeted for junior developers?
Or also, it can be helpful for senior devs?

Regards,

Germán

Hi Laurentiu,

How quickly is the idea of the book For a junior developer?
Maybe it can be read in a week?

Similar to a reference book?
(as a good starting point).

Regards,


Germán

Hi Michael,

Is there any example like state management on the server-side?
Similar to a state machine?

I understand by decoupling the micro-frontend should be necessary, in particular, with complex workflows.

Regards,

German

Hello Craig,

I see this new edition has Reactive paradigm; how much new stuff does it have, and how do you define which modules of Spring ecosystem are included?

For instance, spring-state-machine (some kind related to old-spring-webflow seems not to be there) doesn't seem to be included.

Regards,

Germán

Hello,

Does the book make references to failure use of Scrum?

Or failures of Scrum itself?

I feel still hype on Agile processes and see how we can remove overhead from it.

Regards,

Germán

It sounds good... first we need to understand well about concurrent paradigm for later use any specific API.

Hi Marco,

Thread Safety chapter is about good practice of concurrent programming only, or also using Java API, including CompletableFuture ?

Regards,

Germán