>денвер Лол, до сих пор кто-то это говно использует? Пхпшники какие-то отсталые люди.

@kagami http://www.eg.ru/daily/cadr/29741/

@kagami вообще, это перевод пасты с реддита, я просто обосрался

@kurkuma Для меня.

@kurkuma На реддите используют денвер? Да ты пиздишь.

@kagami там был LAMP, я перевел под рашкинские реалии

@kurkuma И что ему насоветовали?

@kagami It really depends on the company. Here's my general list for an entry level person. I wouldn't expect you to be an expert on all these things, but to me this is all basic web-developer stuff. This is actually my 'web developer' list which usually is a superset of 'PHP developer' - there are certainly large companies where you can get away with knowing 0 about front-end development. HTML & CSS CSS 3, What browsers support what selectors at what version. Its unlikely anyone ever memorizes all of this, but devleopers should have an inkling, and know where to look it up. CSS Based layouts, rather then table layouts. I still still student projects that use tables for layout. Have experience taking a professional design (PSD) and building it ( HTML + CSS ) Security SQL injection. Be aware that using something like php's addslashes() is unsafe, and that even built in database functions like mysql_real_escape_string() are unsafe in certain circumstances. Developers should understand prepared statements and how to use them. Should have an understanding of XSS / CSRF Should understand session hijacking and how to defend against it Usability and Testing Be aware that not all browsers are standards compliant and that the same browser under different operating systems may behave differently. Be able to troubleshoot front end issues on a variety of platforms and browsers Basic familiarity with UX issues: Fitt's Law, Human Readable Error Messages, Latency Reduction. The stuff that programmers deal with, not design issues. General Coding Developers should be taught how to write readable code. I see a lot of graduates with 500+ line methods, or variable names that don't mean much. Naming is hard, it should be taught. DRY programming practices Why globals are almost always the wrong decision What MVC is, and how it applies to web development Javascript Understand the prototypical object system that javascript uses, be able to write Object Oriented javascript Be able to use with high familiarity at least one of the major libraries: jQuery, mootools, prototype. Developers are more likely to run into jQuery then anything else Be able to write DOM manipulations in javascript without the help of a library if pressed and having documentation. We almost never do it in practice, but one should know what goes on under the hood. Understand variable scope in JS, including ugly little corners like variable hoisting How AJAX works All about lose typing, and the inherent insanity in JS Functional Programming (ie. functions are objects in JS) SQL How to write queries without a framework: SELECT, UPDATE, INSERT, DELETE Understand joins, and how the different types work Understand self-joins SQL Injection (Yes, listed twice) Stored Proceedures Triggers Understand Foreign Keys, and CASCADE Understand and show use of proper indexes. Difference between persistant and non-persistant connections PHP Object Oriented Programming principals, including inherentence, interfaces, abstract classes Able to develop projects with at least one major framework: Code Igniter, Zend, Laravel, Fuel, Cake How to handle user input How to handle database connections in PHP (ideally with PDO, failing that with mysqli_*) How to create persistant vs non-persistant connections How to use a debugger vs. how to debug code with echo statements Server This stuff is more 'advanced' - I wouldn't pass over a candidate who didn't know these things, but it seems the ones who actually learn all the other important things learn this too basic ability to do things on a unix based system via the command line how to set up a vhost under apache understand how IP addresses work with domain names know how to check access and error logs to troubleshoot problems Overall Should be able to build a basic CRUD webapp from scratch from start to finish.

@kurkuma Проебал форматирование. Лучше ссылку бы дал на пост.

@kagami лень, смотри в топе /r/php

@kurkuma Нашёл. Олсо, что характерно, ни одного вопроса по части алгоритмов и структур. Успешные пхп-кодеры успешны :3

@kagami > алгоритмов и структур говно для задротов, успешным людям это ненужно

@kurkuma Все верно. Все полезные алгоритмы и структуры уже давно в библиотеках.

@plhk Лол да, то-то постоянно видишь код, где строки объединяются через конкатенацию, где списочная структура используется для поиска, то и вообще какую-нибудь хуйню на O(n!) напишут. Чтобы использовать правильные алгоритмы и структуры, надо их для начала знать. А не ололо-заюзаю что найду в stdlib, авось прокатит.

@kagami >O(n!) На данных тупикал пхпбляди без разницы вообще.

@kagami > строки объединяются через конкатенацию Что в этом плохого? У тебя есть две строки, нужно склеить. Что будешь делать? > списочная структура используется для поиска Что в этом плохого? У тебя есть массив с хуйней, нужно найти в нем одну из хуйнь. Что будешь делать?