Win a copy of High Performance Python for Data Analytics this week in the Python forum!

Jorge Ruiz-Aquino

Ranch Hand
+ Follow
since Sep 25, 2017
Cows and Likes
Cows
Total received
1
In last 30 days
0
Total given
0
Likes
Total received
14
Received in last 30 days
0
Total given
11
Given in last 30 days
2
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Jorge Ruiz-Aquino

I would say is an amazing focus.
Thank you Jamiel.
Hi Jamiel,
Congratulations on your new book.

How Corda is different to other libraries like BitcoinJ and HyperLedger?
Where Corda comes in play?

Thanks.
Yes, I was surprised to see a topic about iframes in your book. Seems to be more like why not to use it though  

I have not hear before about the services you mention (podium, zalando tailor). I'll check them out.

Thank you!
I would say that the decision whether to apply the micro frontend architecture should be taken from the beginning.
From what I see, micro-frontend involves the architecture of the project as a whole. So changing in a later stage from my traditional frontend approach to micro-frontend will cause to refactor a lot of things and this, in big project/team/company will need a whole set of regression testing, just for mentioning one.
But I think Michael Geers would have a better advice on this.
Hi Michael Geers,

How many approaches do you promote to accomplish the rendering of the micro-applications?
I can think of Ajax + container elements like DIV.
Wow, that's an amazing way of how to break the soft-class feature of Javascript. Although as you say, maybe "most programmers will prefer the class syntax".

I see this approach a bit complicated as the developer needs to take care of several things if he wants to do it right.

Anyways, it's always great to see how things can be done in a different way in Javascript.
Tahnks!
Cay,

In the Chapter 3, there is a "Hard Objects" topic.
It explains how to create Hard Objects in Javascript?

Thanks.
Congrats on the new book Cay.

This book, just as the name, follows the same teaching approach as the "Core Java SE 9 for the Impatient"?
It was really nice and effortless to read that book.
There is a link to the contents where you can find the chapters:
7. TEST-DRIVEN DEVELOPMENT
10. END-TO-END TESTING
11. CONTINUOUS INTEGRATION & CONTINUOUS DELIVERY

These chapters are not included as free samples but for answering your question, yes, the book covers those topics.
Although not specific, I would say that the chapters 9 & 12 cover part of the topic "integrating testing in a corporate environment with other existing tools".
But I'm sure Lucas da Costa would respond this questions better.
Lucas da Costa congrats for your book!
This is one of the awkward interesting questions.

I was reviewing the available contents in Manning's site. I noticed that several concepts are similar to general testing, like the atomicity, assertions, mocks, stubs.

So, apart from libraries or tools?
How the concepts of testing JavaScript applications  differ from testing other languages (let say Java)?

Thanks.

Junilu Lacar wrote:As a newbie on a real-world project, you should have been told that Copy/Paste programming is grounds for immediate termination of employment.
Seriously though, stop making this OK just because you're a newbie. This should be Lesson #1 on Day #1 : Copy/Paste coding, BAD! BAD PROGRAMMER!


so true and funny.

Junilu Lacar wrote:I think you meant "peer reviews" but "pair reviews" works, too, if you were referring to the instant code reviews that pair programming affords you.


Yes, my bad. I meant peer review. I updated my comment.


Junilu Lacar wrote:More than likely the average "experienced guy" in large corporate settings ... has practically little to no experience in refactoring or unit testing.


I'm in a large corporate (no-unicorn). So, I plenty agree with you.

Junilu Lacar wrote:I'd bet that if you brought up this Five Lines of Code to your lead developer, there's a good chance you'll get a strange "WTF you talkin' about?" look back.


Challenge accepted.  

Junilu Lacar wrote:larger scale refactoring efforts that require their own "tickets" (ugh) should be reserved for legacy code that you have to maintain.


Junilu Lacar wrote:People with less design/development experience will have a less keen sense of "smell"... You won't refactor something that doesn't smell to you...


I agree with these.
Let's say, there is a legacy-like system with newbie folks working on it making a combination of factors causing more code that need to be refactored.
Newbie folks tend to c&p existing blocks of code to replicate some logic ending with tons of code duplication.
Also they tend even to replicate the old friends "hundreds" and "thousands-lines-method".
However, here is where the "peer reviews" come handy. Hoping that the experienced guy have in mind good practices and the sense of "code smell".

Thank you for these insights from you both.
Hi Christian,

How do you approach code refactoring in real world?
Do you do iterations? What do you refactor first and what later?

There are many recommendations of what to refactor and how, but not a guide of how to push the overall effort.

Thanks.
Thank you Christian,

It makes sense to me.
Although I was pointing out the code duplication I do really like your approach to the rest of the code. It also makes sense to a lot of the code in our system.
I hope I can join at today's streaming.
Christian Clausen, maybe a better example would be the snippet I posted in the thread Algorithm to eliminate code duplication where there is a code duplication in order to process remaining data, however that duplication could be avoided by adding one more counter and check in one single block of code.