I know how to create something like http://www.website-name.com/xyz, but I wish to create a link, like http://www.xyz.website-name.com. I have been searching for this for sometime now, and unable to find any answer. Can someone please help, as I am new to web development?
I think you are looking for something called - subdomain. Maybe this would help: Subdomains
I am currently planning to transfer my cooking recipies from a word document into an offline webpage. I have a (very) basic understanding of html, css and javascript, but never really got in contact with a database.
Can you recommend any database that I can use for my project?
My requirements are:
ideally future-proof -> widespread usage, state of the art and exportable for future use
broad applicability (maybe useable in future projects), not just for cooking books
no php, since the page is offline a server should no be necessary
no need for a fancy user interface. I would prefer to just enter and change the data directly in the database, like entering text in excel. I do not want to use commands like "update" or "insert" to add data.
I read about Excel, MS-Access, mySQL, MariaDB, …
Can anyone recommend a database for my purpose? This would really help me out! I am lost in the jungle of opportunities.
Thank you in advance
Best regards
REn0
Edit: I uploaded an image to clarify my idea. Unfortunatly stackoverflow does not allow me to embed it into the post, thats why I only posted the link
https://i.stack.imgur.com/6nvx1.png
One of the tenets of Rails is you shouldn't really care what database you're using: that's all abstracted for you. I know it's kind of diverging from your skillset, but Rails would be a great approach for an application like this, especially if you want to deploy to a server instead of running it locally down the road.
Check out some 12 in 12 tutorials by Mackenzie Child, https://www.youtube.com/watch?v=QhdzE1yNs-0
I am on my first job after completing my studies. My company does not follow any good coding or documentation practices, just a few basic rules. So there is no documentation of my project or any comments in the code. My only source of help are my teammates who clear my doubts if I dont understand something and they explained me the basic structure of the project.
So any advice on how do I understand such a project considering I am completely new to the corporate world and have no prior experience to understanding projects.
What steps should I take to understand the project better?
I read the below link
Advice on how to understand a project with long history quickly
but in that situation he actually has docs to read.
Thanks for your help.
I remember stumbling onto a list of basic algorithms to implement in a new language to get your head around how the language does thing, but I seem to have lost the link to it.
What simple tasks/code snippets would you recomend one undertakes to pick get a good feeling of a language?
I'm not talking developing large applications or anything the kind of things I'm thinking about are writing a linked list then extending it to a doubly linked list. Implementing various sort/search algorithms, etc.
Excercises that would help somone who knows how to program in one language get up to speed as quickly as possible in a new language.
I usually take a couple of random problems from Project Euler: http://projecteuler.net/
I like the exercises from CodeKata. They are not too easy and not too difficult. Strech your mind with them!
I really do like the problems at spoj.pl. Can be done in quite some lanuages. Yours may be one of those.
I read somewhere that creating a Blog is the HelloWorld 2.0, I saw you don't want big applications but I found worth to share this
You might try this list from JobSnake to familiarize yourself with a new programming language.
Attempting to write compiler/interpreter for it. This opens up many obscure corners of the language and also makes you understand the reasons behind features of the language.
Everytime I have/want to learn a new project, I force myself to find something to code.
But to be sure I did it well, I always want to be able to check my code and what it ouputs.
To do so, I just try to do the same kind of stuff with languages I know and to compare the outputs. For that, I created a little project (hosted on Github) with an exercise sheet and the correction for every language I learnt. It's a good way to learn in my opinion because it gives you a real little project.
I'm not really asking about how programmers learn how to program. More about specific technologies. If I wanted to learn Hibernate, how do I know what I should know prior to Hibernate? Should I learn JPA before, during or after Hibernate? Is there a better solution to Hibernate? (And I'm not really looking for information on Hibernate specifically)
Maybe stackoverflow is the place to find these answers, but it seems like with the shear vastness of frameworks, apis, libraries, programming languages, platforms, and whatever other techie word you want to use, it takes an extremely long time to come up to speed on what technology to use, when and what you need to know prior to using it.
Sometimes the best way to learn is to just dig in to a framework. Sure, you could use someones wrapper API around something, but if there is something wrong w/ hibernate, then you wouldn't know what's happening.
And to answer "how do i know what i should know prior to hibernate", you don't, that's why you are learning. When learning about c++, started out with simple data types, but i didn't know about pointers yet, didn't need to, but i learned about them when i got there. Just gotta jump in and start playing around.
I use Wikipedia to compare various technologies to copmlete a task, although it can be incomplete with regards to commercial closed-source frameworks (probably because fewer people have access to them).
For specific technologies such as Hibernate, Java, JPA, LDAP (OpenLDAP in particular), Log4J, anything Apache: they all have wikis and/or forums associated with the product that are usually more helpful than a Google search for learning. Many even come with tutorials and you should try them.
Find a book on the subject and read it. Then email the author with additional questions. Most of these authors are more than happy to help especially if you've bought and read the materials they worked so hard to produce.
If that's still not enough for you, go to a conference covering the subject, if you can make it. Again you can meet many of the people responsible for maintaining and/or creating these technologies and I've found they are always willing to answer questions.
go to sites like Coding Horror, Slashdot, Techcrunch etc and find out what people are talking about. Usually if something is popular it's probably something you might want to talk a look at.
There are these things called "books" that are filled with all kinds of knowledge.
A lot of the time the documentation and/or tutorial for any technology or project will mention what prior knowledge is assumed or useful.
So for example hibernate: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#tutorial-intro
"This tutorial is intended for new users of Hibernate but requires Java and SQL knowledge"
For me, the things that have helped my career and taught me what questions to ask are:
Podcasts -- .NET Rocks, etc., which introduce and discuss new technologies and put them in context
Join your local users group, and stick around after the presentation to talk shop with the folks there; you can learn a lot just by hearing what other people are doing and what they are working on learning next
Just look around online and start trying to use whatever tool/technology your trying to learn. As you try to learn one thing, you'll realize your lacking knowledge in other needed areas. at which point you can repeat the process of looking around for this new item you need to learn.
for example, maybe you want to learn Rails, so you start following rails tutorials, but you realize you suck at Ruby. so then you start to focus a bit more on the details of Ruby, then come back to Rails with a little more knowledge and continue on till the next roadblock. this isn't really totally correct, but you get the idea.
you won't always find a full guide of how to use everything. just give it a shot and work it out on your own if you have the time
There is an infinite number of things one could learn. Maybe a better approach would be to think of a project that interests you, or join an open source one, and then learn what you need to know to accomplish what is needed in that project. When you're done, pick a new project that might include new things not learned in the last project.
As far as free sources are concerned, as a .NET programmer I like www.asp.net, and there are many others, such as the ASP.NET quickstart tutorials at http://quickstarts.asp.net/QuickStartv20/default.aspx, C-SharpCorner is good, too, if you don't mind C#.
If you don't object to paying a little money, Lynda.com is a decent place. They have OK tutorials on all kinds of things, not just programming, and I got a decent grounding in Javascript using one of their tutorials. They are adding new things all the time, so if they don't have something on Hibernate now, they may later on. I think their basic rate is $25 per month, but you can just pay for one month and then soak up as many courses as you can find time for.
Asking a more specific question will get your a more specific answer here. When I want to read up on something I usually head to Wikipedia and then Google.
The truth is none of us have the time to read everything we'd like to. So I let someone else do it for me!
The way I solve this is by speed-reading the web - aka. subscribing and reading to other peoples blogs.
Everytime I come across something I'm not familiar with I google it.