Which is the best city/town to spend days walking around the streets?
Which is the best city/town to spend days walking around the streets?
Full fledged web development seems difficult from the outside since there are too many components involved in it, namely, Javascript, HTML, XML, JSON, Server side business logic(language and the framework), calls to database(may need yet another framework), web server and its configuration/deployment.
I think the following steps should get you through the brick walls.
1. First things first, choose a technology stack(and this should be the answer to your question).
How to choose? Let’s lay down some criteria, I’d go for the stack which has
We cannot forget the legen-wait for it-dery Joel Spoelsky’s
http://careers.stackoverf
It does cater to India too.
Are there alternatives to specialist job boards like HasGeek?
Willing to look east? India? Then there’s a perfect place.
http://en.wikipedia.org/w
This place is on the cusp of serious expansion, it’s only a matter of time. But until then it will have abysmally low cost of living. Lot of tech schools around that place, hence lot of people looking for tech positions. Plus lot of techies wanting to return to that place, since it’s their hometown. Since there are no good jobs around that area, people have to forcibly move to metros like Bangalore.
Quite a few startups are already up. Like I said, it’s only a matter of time.
What are the best cities to find a low cost of living, yet a high number of people looking for web/tech positions?
In most cases, UI related code is handled by the one of the newer breeds like Python, RoR etc. The server side engines(backend) are mostly written in Java.
Flipkart.com is a prime example(Indian startup, supposedly worth $1B now). It has a mix of technologies including Java and PHP.
The newer frameworks beat Java black ‘n blue as far as UI development is concerned.
What are the most interesting startups that use Java for their platform?
Read text from anywhere, but just learn to solve the following 15 exercises. This is the trick I use to learn a new language.
What you think is bloating the code right now, may be immensely useful later. You may think currently there is only one implementation. In future there may suddenly be many, of which you had never thought/dreamed about.
From another perspective, if the code goes wrong(messy) just once by a bit, the subsequent maintainers of the code will make the code more and more messy and take the project to a point of no return over a period of time. And needless to say, refactoring is very expensive.
So we need to really think and make sure we are not making that first mess. Of course, at the EOD, its the developer’s prerogative, the rest can only issue caveats.
Is it a good Java practice to create an interface if there is only one implementation?