Herberto Graca

Talks

No talks so far

Comments

(Show Details)
(Hide Details)
Rating: 4 of 5 
(20.Dec.2012)
Your code sucks, let's fix it!
I think you probably figured this out from the talk, but anyway here it goes... You have 2 things to make better in this talk: 1 - All examples should be PHP. Personally it doesn't make a difference to me, because I understand you want to teach the concept and the details are not the main issue. However, some ppl will only fully understand it if its a PHP example, and some ppl are just annoying and will complain its not PHP. To be a 5* talk you should make all examples PHP, thus avoiding both problems. 2 - The repaint(false) example. Fix it by making i.e. repaint('flower'). This way everyone will say "the method will repaint a flower in the screen" and you will say "it seems so, but looking further at the code, it will repaint the whole screen and animate a flower". From here you will immediately uncover and explain the 2 underlying problems (readability and breaking the single responsibility principle), and from there how to fix it. Another overall thing you should improve is the talk mood lines. In your case, the jokes. Your jokes have a good purpose, are nice, and work. However I've watched 3 or 4 of your talks and they are always the same, which makes you sound fake. Get some more funny lines, funny stories, everyone likes a short funny story and Im sure you've had a lot of them as a developer. And anyway your Brazilian so you shouldn't have a problem finding fun stuff to say! ;)
Rating: 2 of 5 
(20.Dec.2012)
Debugging with Pry
Hi, I have no experience with ruby so my comment is the view of a first contact with the contents of your talk. In the end of your talk I was fully convinced that you are a guru developer, very active in open source projects. However that is not the aim of a talk. The aim is pass on knowledge, and the way you do it must be adapted to the audience you have. In this talk you had a mix of ruby and php developers, so you must have figured not all were experienced with ruby. These are the problems in your talk: - You spoke too fast - At some point you gave an example of php tools, which is good, so you didnt ignore the php ppl, but it was spoken too fast and just mumbling. There was no place where the name was written so I couldn't get it. This is why slides are used for. - You spoke of the problem and than explained the solution, which is good. But you just spoke it. There should be a clear, short, message about the problem that stays there while you explain the solution. Or at least for some time, so ppl can digest the problem. This is why slides are used for. - You gave real time and real life examples, which is great. However if ppl don't see your command line stuff clearly and have time to digest it, ppl get lost in the example. Again, there should be a clear explanation of the example, that stays for a while for ppl to digest it. - Real time examples are great, but you always have the risk of things going wrong, and they did. First you didn't have some stuff installed, than something else happens, and so on. Its great that you make real time examples, but you have to make, at least one test run before the talk. - Next time, if you plan real time examples, make sure your hosts have a chair for you so you can properly see whats in your screen. I give 2 points because you definitely knew what you were talking about, you were available for all questions even if out of scope. Keep it up, Im sure you will get better.
Rating: 2 of 5 
(20.Mar.2014)
Having async fun with reactphp
You had a good positioning on set, you had a good movement during the talk ( didn't cross the beam, were positioned enough on the side as to not cover the screen for the ppl on the sides), you spoke with the right volume and clear enough (although it could be better), the slides were plain and visually clear which is great, and you clearly knew what you were talking about. However, this talk was not adequate for the audience you had. Maybe it would be good for ppl with experience about nodeJs or even reactphp, but I don't think the vast majority of the audience has any of those, I think most of them were there because reactphp is new to them and they wanted to learn something. I'm guessing about other ppl so I might be wrong, but that was definitely my case. So, if you wanna do a presentation for all levels of knowledge about the content, the first thing to explain is the concept (ie before making a chair you have to know what a chair is, why it's used and how it's generically used), only after that you start explaining the implementation details of the concept (ie how the chair is actually used and/or built). Let me start by stating that different ppl learn different contents in different ways. However, concepts are somewhat abstract and, as such, they are better explained with drawings, sketches, schemas. The audience in a talk will not have the time and/or focus to understand a piece of code, specially if they don't have experience with the subject. And they will surely not remember the code examples. There's just too many details. However, a good schema, they will remember for some time and will help grasp the concept. And of course the concept will be remembered, if they understand it during the talk. You also talked about other libraries, which you assumed ppl were familiar with. Well, I wasn't, I still am not, I don't remember their names, nor what they are used for, nor why were they relevant for the talk. Again, a schema with an example of what they are used for, why they are needed, why they are a relevant example, would have been great. Bottom line, I still don't know what is reactphp (nor nodeJs). Whats new about it? Ok, it provides for async calls, but we already did that with ajax a few years ago, so what's the difference? When should we use it? Why couldn't you do your map project with a regular framework and had to do it with reactphp? What do you mean by "symfony blocks everything"? I'm sorry I'm giving you such a negative feedback, you do seem to have a lot of knowledge about the subject and I'm sure you have all the answers to my questions, so I truly hope my feedback improves your talk and presentation skills so next time you pass on to me some of that cool knowledge you have.
Rating: 4 of 5 
(25.Jul.2014)
Graph Databases with PHP
Knowing that this was Michelle first talk about this issue, it was an excellent starting point! Her positioning in the room was good (everyone could see her and the screen clearly), the slides were clear, she talked loud and clear, live demoing was an excellent idea, simple and effective. Also loved the occasional funny "Yeeey!", which is an excellent practise when making presentations, both to create empathy with the audience and to help ppl regain focus on the presentation. Things to improve: - The audience will always have concerns about stability and performance. There should be something mentioned in the beginning about: - Who uses GraphDBs/Neo4J - Who develops it and why its gonna be around for many years - How fast is it to develop with it, when compared to RDBMS, where you have to plan the whole DB design in advance, in detail - How fast is it when compared to MySQL. It would be good to have a few different benchmarks, but it would be excellent if you would have your own benchmark. - It's easier for ppl to connect with a new concept if they can relate it to something they already know. I would suggest that in the beginning of the talk you clearly relate RDBMS with GraphDB, by relating a table to a node type, a record to a node, and explaining that while in RDBMS relations are pre-established between tables/nodetypes, in GraphDBs relations are not pre-established, they are created on the fly and directly between records/nodes. - In the end it would be great to have a more complex example of a situation that is possible/easy to do with GraphDBs but impossible/difficult to do with RDBMS. Hope this helps improve the talk, but as I said before, it was a very good talk already.
Rating: 5 of 5 
(19.Sep.2014)
Models and Service Layers; Hemoglobin and Hobgoblins
It was one of the most interesting talks I've been to, if not the most! The thematic is of great interest. The speed at which Ross talks can be a problem for some ppl, but for me it prevents my brain from getting bored and start thinking about something else, so it helps me keep focus on the talk. The hat is an excellent detail. It's something unusual, and humans tend to naturally focus on stuff that is unusual. It has the same effect as if the presenter moves slowly while doing the talk. As others commented already, after the 2/3 of the talk, if got difficult to follow, its problems and advanced solutions that I have not thought of before. At this point I felt a problem following the code because the "before" and "after" code samples were in separate slides and my short memory span did not allow me to read, understand the code and understand the problem for both slides and then compare them in my head. I would suggest that you put the code in some way that we can compare the changes in only one slide. Nevertheless, this was definitely a 5* talk.
Rating: 3 of 5 
(21.Nov.2014)
Profiling PHP, A dive into your application
It was pretty good for a first timer! The slides were good, Dennis posture was good throughout the presentation and the dictation was also good. Dennis clearly knew what he was talking about. On the down side, I could notice he was a bit nervous, which is normal but can be improved by doing more talks and finding ways to release that stress. If we look at other talks, I would say 95% of the talks start with joke(s) and/or some exposure on a personal level like "When I was coming here this and this happened...". This kind of start helps create empathy with the audience which in turn helps the talker release stress, feel more confident and comfortable. I also felt the presentation lacked some more use cases, some more in depth usage examples. I find this more serious than being nervous. Nevertheless I think Dennis is just starting his path with Linko and has a nice list of ideas for the future, specially the integration with Codeception, and I am really eager to see how his work with Linko evolves in another talk in the future.
Rating: 2 of 5 
(30.Jun.2017)
Keynote: Beyond Code
The subject is interesting but I found the talk itself boring. It lacked "energy", it was very monochordic, nothing stoping me from "falling asleep". People usually can keep focus for 10 to 20 minutes. Then they loose focus. This will always happen, but we can just ignore it and have ppl randomly loose their focus, or we can be in control and break their focus ourselves with a good joke or a funny image or changing the tone of our voice frequently or whatever. The point is that if we can control when they loose focus, we can control when they have focus on the important stuff we want to say.
Rating: 3 of 5 
(30.Jun.2017)
Docker from Development to Production: Streamlining the CI/CD process for the new BALR. e-commerce application
I expected more technical content. The QA was quite good though.
Rating: 4 of 5 
(30.Jun.2017)
Introduction to the Semantic Web
Interesting contents, clear future potencial in thus subject, specially if we combine it with AI. Energetic, enthusiastic and knowlegable speaker. Not a great impact on my day to day work as a PHP developer though.
Rating: 1 of 5 
(01.Jul.2017)
Continuously delivering containerized, highly available microservices with proper context boundaries and messaging integration
Usually Mathias gives worthy talks but this time i was disapointed. I was expecting much more technical content. The ideas explained were not very deep, we can easily grasp them by reading a few articles.The conference ticket should be worth more. It also saddens me to say that it sounded a bit like "don't listen to ppl with no experience in microservices, i dont have experience with microservices, go buy my book about microservices".
Rating: 3 of 5 
(01.Jul.2017)
Beating the Pentester
Good talk about an important subject often neglected. The speaker seemed to be in control of the subject. Would have been nice to see more code examples if what to do and not to do.
Rating: 4 of 5 
(01.Jul.2017)
Empathy As A Service: Supporting Mental Health in the Tech Workplace
Great talk on a very important and difficult subject.
Rating: 5 of 5 
(01.Jul.2017)
Elastic scaling in a (micro)service oriented architecture
Excellent talk! The speaker knew what he was talking about by his own experience, the subject is cutting edge and the talk had the right granularity/depth. Best talk so far!
Rating: 2 of 5 
(01.Jul.2017)
The (Awesome) Future of Web Apps
It was an interesting talk, the presentation was well designed, the speaker was knowlegeable and fluent. However, there wasn't even one word about PHP. I paid a ticket to attend lectures about cutting edge PHP, not about mobile apps. I expected some connection of PWA with what I do as a PHP developer.

Events They'll Be At

No events so far

Events They Were At

© Joind.in 2017