222 reputation
211
bio website danielribeiro.org
location Florianópolis, Brazil
age 24
visits member for 2 years, 10 months
seen Nov 30 at 11:06

Daniel Ribeiro is a Senior PHP Developer, Evangelist and Speaker in Florianópolis, Brasil. Currently working as a Senior Developer at KnpLabs and a member of PHP Santa Catarina (PHPSC) – brazilian local PHP community –, he is a Zend Certified Engineer, working with PHP since 2006.

He loves to share code and contribute to open-source projects. Usually, he is focused on TDD, object-oriented design and code refactoring. He also has experience on leading development teams focusing best practices and software quality.

Contact him at drgomesp@gmail.com


Mar
25
awarded  Notable Question
Jan
29
comment Should I blog about specifically about programming in English or in my native language?
I've already made my mind: technical stuff I do in english. Personal stuff, in portuguese (my native).
Nov
27
awarded  Yearling
Aug
9
awarded  Popular Question
Feb
26
answered Should I blog about specifically about programming in English or in my native language?
Jan
14
revised Why does PHP have interfaces?
added 823 characters in body
Jan
14
answered Why does PHP have interfaces?
Jan
5
comment What does it mean to expose a C++ code publicly as a C API and what are the advantages of doing it?
Can I keep using .hpp extensions or should I change all of my headers to .h?
Jan
4
awarded  Nice Question
Jan
4
comment What does it mean to expose a C++ code publicly as a C API and what are the advantages of doing it?
That's a great answer. Can you give me an example of the extern "C" stuff, that I didn't get?
Jan
4
asked What does it mean to expose a C++ code publicly as a C API and what are the advantages of doing it?
Dec
30
awarded  Teacher
Dec
30
answered TDD and test automation in applications heavily dependent on databases and user input
Dec
21
awarded  Commentator
Dec
21
comment How deep should we dive into testing different layers
That layer is just there for Drupal, nothing else. We have interfaces to define the layer's behaviour though, despite the platform we are working on. Say we change from Drupal to Magento, we would have to implement those interfaces on the Glue layer to connect to the Magento API just as we did for Drupal. That's why we are not sure to test those classes.
Dec
21
comment How deep should we dive into testing different layers
Thanks for the brilliant answer. Concerning the repository objects, they don't have any business specific code, but they do some specific stuff, such as transform drupal nodes into entities, and that process only is already worth testing, in my opinion. When it comes to test them with a real database, that kind of scares me a little bit. That's why I instantly thought of mocking the database class. It could be an option though, to work with memory, as you mentioned. The fact that we have functional tests, in my opinion, make this an unnecessary thing to do.
Dec
21
comment How deep should we dive into testing different layers
Exactly, our business layer is completed separated from the Glue layer, and we can test it without worrying about anything rather than the business layer itself. But the glue layer, as I mentioned, has its own objects, such as repositories. They are the ones we think we should be also testing.
Dec
21
asked How deep should we dive into testing different layers
Oct
17
awarded  Popular Question
Oct
4
awarded  Nice Question