1,108 reputation
38
bio website
location
age
visits member for 2 years, 1 month
seen May 8 at 15:52

I'm a classical guy with some sense to frontend.

I have a separate opinion on Agile, SCRUM, TDD. I don't think they're that cool.

I'm a big fan of RUP and UML, although nowadays I use this more in UX design than in classical software design as that has largely vanished. I still design my own code before writing

I use dynamic languages like JS, Python and PHP to get my job done. I don't believe that explicit static typing helps you as much as it hurts. When it comes to statically typed languages, my expertise is mostly in Java, albeit haven't used it in production since the Java EE years.


Jul
25
awarded  Yearling
Jul
25
awarded  Yearling
Mar
2
awarded  Constituent
Mar
2
awarded  Caucus
Jan
24
awarded  Nice Answer
Sep
21
awarded  Custodian
Sep
2
answered What scripting languages can be embedded within HTML?
Sep
1
answered Is it possible to implement a completely-stateless multiplayer game?
Sep
1
answered How to document requirements for an API systematically?
Aug
18
revised Guided Questioning iOS App
added 206 characters in body
Aug
18
answered Guided Questioning iOS App
Aug
18
comment Javascript simple code to understand prototype-based OOP basics
BTW, one thing classical inheritance got wrong is to totally separate methods and properties, on a Neumann-architecture machine (ARM, PowerPC, Intel), it's meaningless. This is something that JS does well. And these were very good questions to illustrate how proto-oop works.
Aug
18
comment Javascript simple code to understand prototype-based OOP basics
@WorldEngineer - the question was about prototypical inheritance, of course, everyone has their own expectations on how inheritance works. My personal opinion is that classes are needed, have deep roots in human psychology and prototype is a wrong way, but if I had 2 cents for every dev who doesn't understand prototypical I'd be a millionare, so it's worth answering it again and again.
Aug
18
answered How do you break out of the role of a code maintainer?
Aug
18
reviewed Approve suggested edit on Javascript simple code to understand prototype-based OOP basics
Aug
17
comment Javascript simple code to understand prototype-based OOP basics
@WorldEngineer the original question was perfectly answerable.
Aug
17
comment Javascript simple code to understand prototype-based OOP basics
@EduardFloreniscu: I did answer the original version.
Aug
17
answered Javascript simple code to understand prototype-based OOP basics
Aug
14
comment Best Practices when extending a project
See, I did complete refactors on Alexa Top100 website... and it's an e-commerce site (hotel bookings), so it was important not to break, but I had to refactor a few thousand lines as noone else dared to touch it, when it was only 200, so they only added their stuff when change was needed...Oh, the code was in Italian, I don't speak Italian. The fully refactored (not rewritten!), English, MVC code went into production a week later, and it does still run. Oh, and it was in PHP, forget Eclipse's analysis. Courage and knowledge can help code quality.
Aug
14
comment Best Practices when extending a project
The idea is to avoid the risk of breaking something and not knowing why - this is a bad advice: this is what makes code grow like spaghetti. You have to create an environment where there's OK to break something and you have meaningful feedback (sometimes even at the cost of some angry minutes from the users), otherwise you'll ruin the source code in days. Perhaps ask some users to use a test version, as the users are the main source of how the thing is supposed to work, the only problem that they can only tell you this when it doesn't work that way.