beberlei

thanks fixed!

Hey one of the developers here. This project started as a side project six month ago, however several of our customers quickly demanded we make it a product. We are excited to release it to open beta today.

Our main focus with this product is generating deep insights into PHP applications. Much of our experience with different frameworks, shops systems and libraries is automated here to help developers fix performance problems quickly.

I would appreciate all kinds of feedback and will answer all your questions.

Getting out of my comfort zone here, as I feel we are not ready, but my company is working on a product that is focusing much more on application profiling than NewRelic and less on the monitoring that is built exclusively for PHP:

https://profiler.qafoolabs.com/

We are still in closed beta but not for long anymore. You can sign up for our waiting list if you are interested to hear more.

As for the pricing, we are working on a model that is not per server/host.

So you are sugessting better prematurely "optimizing" every call to be remote from the beginnig? Wouldnt anyone wrap remote services behind a facade anyways instead of directly calling a http client? I fail to see how this leads to an interface that expresses the remoteness more in most of the cases.

Where are the screenshots? I don't want to install this to get a first view of how it looks and works.

the mysql documentation definatly states otherwise: http://dev.mysql.com/doc/refman/5.7/en/innodb-create-index-o...

someone else mentioned it on twitter before, thanks for the hint :)

I mention Wordpress only as great example of "getting this done" approach of PHP. Never did i mention it as example of "high quality PHP code".

phpBB and Drupal have their problems, but they both improved their code-base alot, moving from legacy PHP software to software that is much more maintainable. The road to "high quality software" is long, but throwing software out of the window instead of slowly improving it is not the right solution either.

Both projects have high numbers of unit-tests and can guarantee backwards compatibility and regression free releases in a much better way than most of the software out there in any company, written in any language.

Author here. I wrote this article as a guestblogger for Acquia, which is the company behind Drupal. I don't work at Acquia.

The article obviously uses Drupal as an example, PHPBB and Wordpress as comparison because they are all in the off-the-shelf, customizable category of PHP applications.

Both Drupal and phpBB (contrast to Wordpress) have massively modernized their code bases in the last years and improved the quality of their code. Coming from their original level, this is obviously a huge undertaking and still far away from being "high quality code" as an absolute measure. However their efforts in this space are remarkable.

Given that they have so huge installed code-basis that they have to take backwards compatibility seriously (which is also something that contributes to quality of software), explaining why it takes so long to improve the quality of truly old legacy software.

Compare this with many companies that use PHP, that still don't know what automated testing and quality assurance is. The article tries to highlight how PHP open source software use tools for quality assurance, what tools exist and that you should use them in your PHP projects.

Does anybody else feel that having a track record in solving beaucracy issues can not really be applied that much in getting a legacy IT system fixed that seems right before cardiac arrest?

about that national development team, IMHO developers don't want to work for the government or on government jobs for a very good reason, hence the good ones are normally in the position to skip such jobs. Quality and management of IT projects is much worse in government projects vs private sector from my limited experience.

some feedback from me:

1. the value types are not immutable, which will make it very hard to work with them on larger scale. You should create new instances instead of modifying the original ones, keeping the originals intact.

2. The object hierachy is borked. You are exposing way to much information. Instead of generically allowing to save values and options in the Object, you should specialize the types much more and hide the actual value.

3. You should convert the value when creating the type, using (int) for example, or throw an exception if not convertable. The current converts the values at many places, which increases the complexity of the code unnecessarily.

This is very cool! I could have really used this during my time at university. :)

How about as a next step adding revisions to formulas and making them commentable, working sort of like gists?

it is used without caching, leading to unnecessary parsing of a metadata structure. This is explicitly not recommended for production use and kills the request time here.

Doctrine is explicitly not suitable for non cache usage. You should remove the ORM from the test and use the DBAL only instead if you don't have caching introduced.

Additionally you are not bootstrapping the Symfony cache correctly, you need to run "php app/console cache:clear --warmup --env=prod --no-debug" before running the tests, it might cause cache slams in your benchmarks.

I disagree heavily.

Refactoring tests is as important as refactoring "production" code. Following the four elements of simple design (http://www.jbrains.ca/permalink/the-four-elements-of-simple-...) you can use test refactorings to find better names and detect need for abstractions.

Tests with lots of duplication, for example in the test setup, get hard to maintain and developers tend to abandon them more easily (my own experience).

The blog post shows extract method as well as a second refactoring

Edit: Also see the screenshot here for a more complex extract method refactoring: http://qafoolabs.github.io/php-refactoring-browser/

Currently the refactoring available for extracting code is "extract method". "extract function" is not available yet and may even be implemented as "extract static class" or something, because it may be safer to achieve.

You picked the simplest refactoring, for converting local to instance variable I agree with you, this is easy in Vim.

But still there are some potential problems:

1. The variable already exists in the class. 2. You accidently mark to much or to few lines with ":<,>%"

For refactorings such as extract method the number of preconditions and information to gather is much bigger, such as input and output variables, existance of return statement etc.

We plan to integrate the tool into vim as well, so that you can call the refactorings through vim directly.

I suppose it can be integrated into IDEs. We (the developers) are Vim users, so there is no immediate need for us to integrate it into anything except Vim.

We know that PHP Storm has many refactorings implemented very well, but a command line tool is much more flexible and useable for everyone, not just PHP Storm users.

Now all that i need is a proxy, that reliable allows me to use my own domain as a tent server, proxying to tent.is. ;-)

This buzzed right around the time app.net was funded one month ago, http://news.ycombinator.com/item?id=4418904

Too much focus on Computer Science in my opinion. Udacity already covers CS in detail. The only interesting bit is the introductory chemics course, a focus on physics, chemics, biology and engineering could have set edx apart from udacity.

Very spot on explanation of what is circulating in my head for months now. This seems to relate to the Data-Context-Interaction movement and what Bob Martin calls Entity-Boundary-Interactor pattern in his latest talks.

Very cool.

But this would be even cooler if it would be a timeline of all the projects, organizations I am part of. Sort of the Github Dashboard as a timeline, but with additional logic to group certain events (commits for example) per project to reduce the clutter and with all the organizations in one dashboard (currently you have to use the dropdown to switch between them).

i want information about what this is before having to give my details.

I agree with this opinion. The author lacks historic perspective. New successful businesses automatically are monopolies since they create new markets. This can obviously be seen in tech nowadays since this is all technogicially new.

Historically it was the same and these companies still benefit from their competitive advantage (or were crushed by the state) just to name Standard Oil, Bell/AT&T, BASF, Ford. Just over time did competititors take market share from them, because they became huge beurcratic monsters (as all monopolies do).