Printable View
as of now i want to spend my free time learning that language and as of now i don't have any wants but if time come and i have many knowledge on it then why not use it professionally.Quote:
But I do agree with your points, if he isn't wanting to do it professionally then PHP would be unmaintainable.
yes im sure to do that even i have long enough to make it!Quote:
Originally Posted by Negata
I suppose you could build a "forum" only that it's enough to make it a single thread. Finish each step and make sure it works before extending to the next.
1. Only HTML, no PHP, no database; A page which shows a few posts in a similar fashion as you see them here on RZ.
2. PHP included into HTML, no database; Use the page you have but extend the page so that you have the content for each post stored in an array. Render the posts into the page using contents in the array.
3. PHP, request params, no database; Again, extend from 2, render an additional post which gets its content from the url query parameters.
4. Add input field(s); You don't need to write the params into the address line anymore, the params are sent from the form inputs.
5. Add database; The extra post is stored into database. Render all posts that have been stored.
6. Add javascript (look into jQuery); The post is sent via an AJAX request and then rendered into the page on the browser side.
7. Add user accounts; It's ok to keep the accounts as plain text in your php file if you want, just make it possible to submit a username and password and then use a session so that you're able to assign each new post to the username.
8. Manage user accounts within the db.
9. Add more javascript&ajax functionality; For example look into "infinite scroll", all posts won't get loaded at once but only when the user scrolls down the page and more posts need to be shown.
After these you should have a basic feeling about the essentials, then figure out what you really want to do next with your newfound knowledge. I tried to organize the steps so that each adds on top of the previous one and is not a very huge leap.
I started off working with a small database and just echoing/comparing the results, and everytime I encountered a problem I would Google it!
Basically I've never learnt anything from school in terms of computer programming (apart from VB..). I guess everyone says it, but trust me, Google is your best friend!
So my suggestion is to just Google about small things, like "variables" and use of variables. What define does and what's the difference between "this" and "this", and soon you should pick a good use of the language. That's what I've been doing for 1-2 years. I'm now building a small CMS :-)
negata, my post was more or less a general point of view and usage. i even think u think to far for kojic on the forum example btw lol. a points you throw now, about php can be still good and depending your work, i agree, but when somebody asks for the best (not fastest) way to learn, php isnt the best in this case, since im viewing the way to be professional always. for me a prof has to understand whats going on behind the scene, php doesnt provide. php is easy to reach something very fast like being said, but its not the right choice to understand prof programming, just algorithm understanding wont grow slower by selecting php. about all possible h8ters, this is personal experience. :P
ACADEMiC, wise words, thats how i learned programming on php for 2 years until i droped the bad fractal of design at all. here i want to tell, i learnt c on school while doing php too. but one thing being said, not every source is a wise choice. even stackoverflow is not perfect.
I would typically not even recommend mixing HTML and PHP. The modern practice is to use PHP as a middleware layer (and technically a back-end since it talks to the database). Then your HTML uses jQuery or whatever you want to dynamically render content, and an ajax request to some php page like /posts.php?threadId=<tid> returns post data, and your JS renders it.
The former is unmaintainable, the latter is fairly common in professional practice. Further, if you try to use the former and sprinkle in ajax to "load more" instead of loading another page, you've implemented both, and why not just start with the better approach initially? :)
It's the deep end of the swimming pool and not everyone is up to starting there.Quote:
Originally Posted by jMerliN
thanks for all your suggestion, ill try Negata's guide because i think this is simple and easy to understand for a newbie like me.
It's not a guide in that you'll have to do all the work and find out how-to's :)
yes like a quiz :blushing:Quote:
Originally Posted by Negata
Learn to code | Codecademy - beginner tutorials for python, php, javascript and others
the deep end is assembler :PQuote:
Originally Posted by Negata
You'd be talking about cave diving now :)Quote:
Originally Posted by VibeTribe
Then what is microcode and machine code itself, also manually manipulating CPU cache, and understanding the branch prediction and caching algorithms in the CPU?Quote:
Originally Posted by Negata
IIRC, if you have a certain key, you can re-write any Intel core processor to anything that uses the microcode, so it could probably implement other architectures. Though I don't think anyone outside of Intel has access to those keys, because for some reason they don't want us to be able to reprogram our processors. I can definitely see security concerns, so maybe it's a good idea, but your CPU is basically a tiny little computer in itself, and you could probably run some operating system out of cache alone, and that would be f'ing awesome.
Cave diving without any diving gear, perhaps?Quote:
Originally Posted by jMerliN
Whilst battling underwater lions that shoot lasers out of their eyes, and then it's still a maybe?!