What wished to know in the early days of your web development career ?

Every big Journey starts with small steps. Gone are the days where you could learn on Job without out formal education of the subject-matter. There is too much competition out there. As starting web developer you should know basics of coding and languages like HTML, CSS and Java. 

I remember there was little assistance available on line,with no sign of Google, and limited resources of the relevant books. Now the resources available online and offline are rich, you can get all possible answers on google, practice your basic coding in real time environment with websites like "Code Academy", user friendly software like Adobe Dreamweaver. 

The key is how agar are you to learn, and how much time you are prepared to spend, opportunities are endless.

Tauseef Sarwar

www.creativexireland.com

0ne thing is 4 sure ther is no end to Learn while u Earn (parallel)

Nowadays I am learning laravel framework, I wished to know node. js i am also spending time learning javascript perfectly i think this can help me to learn javascript framework. 

Early days of web development career... bro you r'ly askin' too much :D

I remember learning web design in MS Front Page... then I started to learn HTML and CSS, and got annoyed with Front Page trash code :D Eventually ended with Dreamweaver (anyone remember it?).

Anyway I stuck working for one NGO which had website coded in JScript ASP - which is rare. It was hard to find support for it, compared to VBScript ASP. Once MS moved to ASP.NET, I moved to PHP (I regret not doing it earlier :S)

Well then I wanted to improve my PHP coding skills, adopt some of the MVC models, OO PHP coding and etc... somewhere on the way I lost momentum and started looking for ready CMS solutions, and ended up with WordPress (which at the time was best documented CMS platform). And ever since, if I need to build website I do it on WordPress. Sometimes building my own template or heavily modify existing template - depends on the budget :D

All of this was like a hobby to me, since my professional career took different path...

I wish to learn every new for web development

I started career in web development in year and the very first site I worked on was an e-commerce application. There were many technical challenges:

• Bandwidth: Internet connections were not fast like they are today so loading time of each page was the first thing we consider.

• Hardware: RAM, space and processing power were limited so assessing resources required by each script as well as whole application was second thing to be consider. Application algorithm must be tightly packed to perform fast and free up memory after execution.

• Normalizing and denormalizing databases: This action was required (and still required) for optimum performance of any dynamic site and during the era of limited hardware and bandwidth resources, this was a critical task that must be mixed with cleverly crafted queries for fastest performance possible.

• User interface: Ready made solutions, like bootstrap, were not available so making a user interface to give nice look and easy navigation was another key component to be considered. Client side and server side validation, secure login, etc. were also key features

• Security: E-commerce site means security. Keeping user data secure by encrypting critical information, keeping an eye on security updates and fixing recently discovered loophole in the application programming language were essential tasks.

• IDE: Development tools were not too smart. Things went haywire sometimes. :)
• Documentation: Not many tools were available for documentations.

In fact, the question is unclear to me. However from experience I learned some terminology in IT like Web/MVC/Database etc are some of the implementation techniques( and those should remain for implementation only) or they are I/O mechanism. That is there should be some mechanism to 'receive input' (both data and event) from the end user and 'Process' the request and then 'Store Data'. 

We need to focus more on Application than implementation(Web/Database etc.) That is the 'Process'

In addition to this I found more than 60 to 80% of the requirements (from architecture perspective) are exactly same or similar.(for applications. not for system utility software)

We need to come up with a mechanism that can manage all of these(or most) requirements instead of writing code for every applications. In other words we should have a generic customisable framework for application development

Basm allah alrahman alrahim

I wish that I learn PHP first before ASP

if you are just a back-end developer you'll suffer finding a satisfying job !