Modern Digital Website Security: Prepare to face any form of malicious web activity and enable your sites to optimally serve your customers.
Low-Code Development: Learn the concepts of low code, features + use cases for professional devs, and the low-code implementation process.
Stats
Reputation: | 136 |
Pageviews: | 459.1K |
Articles: | 5 |
Comments: | 45 |
Articles
Refcards
Code Gems for Android Developers
Comments
Aug 02, 2013 · Mr B Loid
Aug 02, 2013 · Mr B Loid
Aug 02, 2013 · Allen Coin
Aug 02, 2013 · Allen Coin
Jul 06, 2011 · Gerd Storm
Jul 06, 2011 · Gerd Storm
Jul 06, 2011 · Foo Bar
Jul 06, 2011 · Foo Bar
Dec 28, 2010 · Tony Thomas
I didn't quite understood your question.
You wrote that your compiler showed 4 errors.
That are exactly the same errors I have wrote in the post - lines 7,8,9,10.
Methods cannot be static, private or private. Members cannot be private.
So I don't quite see how it is different than what I wrote. please elaborate, I'd be happy to help.
Dec 28, 2010 · Tony Thomas
I didn't quite understood your question.
You wrote that your compiler showed 4 errors.
That are exactly the same errors I have wrote in the post - lines 7,8,9,10.
Methods cannot be static, private or private. Members cannot be private.
So I don't quite see how it is different than what I wrote. please elaborate, I'd be happy to help.
Dec 28, 2010 · Tony Thomas
I didn't quite understood your question.
You wrote that your compiler showed 4 errors.
That are exactly the same errors I have wrote in the post - lines 7,8,9,10.
Methods cannot be static, private or private. Members cannot be private.
So I don't quite see how it is different than what I wrote. please elaborate, I'd be happy to help.
Dec 28, 2010 · Tony Thomas
I didn't quite understood your question.
You wrote that your compiler showed 4 errors.
That are exactly the same errors I have wrote in the post - lines 7,8,9,10.
Methods cannot be static, private or private. Members cannot be private.
So I don't quite see how it is different than what I wrote. please elaborate, I'd be happy to help.
Dec 28, 2010 · mitchp
I didn't quite understood your question.
You wrote that your compiler showed 4 errors.
That are exactly the same errors I have wrote in the post - lines 7,8,9,10.
Methods cannot be static, private or private. Members cannot be private.
So I don't quite see how it is different than what I wrote. please elaborate, I'd be happy to help.
Dec 28, 2010 · mitchp
I didn't quite understood your question.
You wrote that your compiler showed 4 errors.
That are exactly the same errors I have wrote in the post - lines 7,8,9,10.
Methods cannot be static, private or private. Members cannot be private.
So I don't quite see how it is different than what I wrote. please elaborate, I'd be happy to help.
Dec 28, 2010 · mitchp
I didn't quite understood your question.
You wrote that your compiler showed 4 errors.
That are exactly the same errors I have wrote in the post - lines 7,8,9,10.
Methods cannot be static, private or private. Members cannot be private.
So I don't quite see how it is different than what I wrote. please elaborate, I'd be happy to help.
Dec 28, 2010 · mitchp
I didn't quite understood your question.
You wrote that your compiler showed 4 errors.
That are exactly the same errors I have wrote in the post - lines 7,8,9,10.
Methods cannot be static, private or private. Members cannot be private.
So I don't quite see how it is different than what I wrote. please elaborate, I'd be happy to help.
Dec 28, 2010 · Tony Thomas
That's the nice thing about the internet, you can choose by yourself which information is good for you and which is not.
Thanks for your response.
Dec 28, 2010 · Tony Thomas
That's the nice thing about the internet, you can choose by yourself which information is good for you and which is not.
Thanks for your response.
Dec 28, 2010 · Tony Thomas
That's the nice thing about the internet, you can choose by yourself which information is good for you and which is not.
Thanks for your response.
Dec 28, 2010 · Tony Thomas
That's the nice thing about the internet, you can choose by yourself which information is good for you and which is not.
Thanks for your response.
Dec 28, 2010 · mitchp
That's the nice thing about the internet, you can choose by yourself which information is good for you and which is not.
Thanks for your response.
Dec 28, 2010 · mitchp
That's the nice thing about the internet, you can choose by yourself which information is good for you and which is not.
Thanks for your response.
Dec 28, 2010 · mitchp
That's the nice thing about the internet, you can choose by yourself which information is good for you and which is not.
Thanks for your response.
Dec 28, 2010 · mitchp
That's the nice thing about the internet, you can choose by yourself which information is good for you and which is not.
Thanks for your response.
Oct 01, 2010 · Jared Richardson
Jun 27, 2010 · James Sugrue
Very cool.
Thanks.
Jun 13, 2010 · Stefan Koopmanschap
Hi Jared, I agree with every word and especially the with the conclusion.
I see more and more programmers which are fed up with learning new technologies and especially new working methods.
They excuse themselves by convincing themselves they have a lot of experience so they must have seen everything there is to see.
I guess that to be above average software developer, your hunger for improvement should be higher than your ego.
Jun 13, 2010 · Jared Richardson
Hi Jared, I agree with every word and especially the with the conclusion.
I see more and more programmers which are fed up with learning new technologies and especially new working methods.
They excuse themselves by convincing themselves they have a lot of experience so they must have seen everything there is to see.
I guess that to be above average software developer, your hunger for improvement should be higher than your ego.
May 27, 2010 · Olivier Dangréaux
My previous job was at a small startup company in the mobile business.
We did everything by the book, right from the start. We designed a massive distributed system and we started developing.
As you wrote in this article, we didn't compromised, we were extremely thorough and we wrote excellent code.
The problem was, it took too much time, the financial crisis of 2008 caused our investors to fold back, and by that, close down the company.
A year worth of quality code was thrown down the well.
Looking back I am certain we could get something done even in 2 months and get it out to the public, and when you have users there will be investors.
That was my lesson from that experience. In the real world, sometimes it is more important to be fast than to be good.
And if you are still not convinced, I would like to remind you the story of Twitter.
In case you don't know, Twitter was first written in the most terrible way. The performance, the framework, the technology were all terrible. When twitter just started, no body believed it would survive, since it keep collapsing and it had absolutely no business plan . But it had one advantage over its competitors - since it was first to do what it does it had a lot of users - that's the only reason it survived. After it was clear people are using Twitter it had no problem getting investors again and again (even with no business plan). After Twitter got invested it had no problem rebuilding the application from scratch and writing "good" code.
If Twitter would have been written from the start as it is written today, it would probably be out to the public at least a few months later, maybe even more than a year later. There is a good chance Twitter would not be where it is today, in this case.
May 27, 2010 · James Sugrue
My previous job was at a small startup company in the mobile business.
We did everything by the book, right from the start. We designed a massive distributed system and we started developing.
As you wrote in this article, we didn't compromised, we were extremely thorough and we wrote excellent code.
The problem was, it took too much time, the financial crisis of 2008 caused our investors to fold back, and by that, close down the company.
A year worth of quality code was thrown down the well.
Looking back I am certain we could get something done even in 2 months and get it out to the public, and when you have users there will be investors.
That was my lesson from that experience. In the real world, sometimes it is more important to be fast than to be good.
And if you are still not convinced, I would like to remind you the story of Twitter.
In case you don't know, Twitter was first written in the most terrible way. The performance, the framework, the technology were all terrible. When twitter just started, no body believed it would survive, since it keep collapsing and it had absolutely no business plan . But it had one advantage over its competitors - since it was first to do what it does it had a lot of users - that's the only reason it survived. After it was clear people are using Twitter it had no problem getting investors again and again (even with no business plan). After Twitter got invested it had no problem rebuilding the application from scratch and writing "good" code.
If Twitter would have been written from the start as it is written today, it would probably be out to the public at least a few months later, maybe even more than a year later. There is a good chance Twitter would not be where it is today, in this case.
May 26, 2010 · mitchp
Hi Ramsundar,
It is true that NoSQLs have a lot of advantages over RDBMS but I wouldn’t say goodbye to RDBM&SQL quite yet.
Bear in mind, that in most of the cases, mature applications change their schema almost never.
Sometimes it is more important for an application to be able to insert data fast and synchronically.
In these cases NoSQL is not as good as old time DBs.
Besides, if consistency is important to you NoSQL data stores are totally wrong for you. I mean, can you imagine a bank application which is working inconsistently with data?!
But still, I like NoSQL, I think there here to stay.
Feb 24, 2010 · Daniel Spiewak
Short and to the point.
Thanks!
Avi.
Feb 24, 2010 · mitchp
Short and to the point.
Thanks!
Avi.
Feb 17, 2010 · Frank Kelly
Thanks for the article and code.
Very cool indeed.
Avi.
Feb 17, 2010 · Senthil Balakrishnan
Thanks for the article and code.
Very cool indeed.
Avi.
Feb 16, 2010 · Avi Yehuda
Hi Richard
your definatly right.
I'll fix it in the article.
Thanks for correcting me.
Feb 16, 2010 · Avi Yehuda
Hi Richard
your definatly right.
I'll fix it in the article.
Thanks for correcting me.
Feb 10, 2010 · Timothy Huertas
Hi Ashish,
As a developer I had 2 periods in my life where I was searching for a new job. The first period was in about the end of 2006 where the software job market was overflowing with open positions. Back than it was much easier to get a job. As you said, no matter how I did in the interview, if my expirience was as they requierd they wanted me almost always. The seconed period of job searching was not too long ago, that was in the middle of 2009, where the software job market was at all time low (at least where I come from). Let me tell you, times were bad. They where hardly any interviews at all (I am talking less that a single interview a week). That was when I decided to stop counting on luck and start doing the best I can. And I am not just talking about getting a job, I am talking about making sure that if the same situation will come up in the future I will be prepered. Those where the times I learned all the principles I wrote in the post.
Looking back I am really thankfull for those times. It really made me better and I can see that in my current job, and thats what I am actually trying say in the post - if you are searching for a job, make the most of it.
Anyway, thanks very much for your comment.
Feb 10, 2010 · Timothy Huertas
Hi Ashish,
As a developer I had 2 periods in my life where I was searching for a new job. The first period was in about the end of 2006 where the software job market was overflowing with open positions. Back than it was much easier to get a job. As you said, no matter how I did in the interview, if my expirience was as they requierd they wanted me almost always. The seconed period of job searching was not too long ago, that was in the middle of 2009, where the software job market was at all time low (at least where I come from). Let me tell you, times were bad. They where hardly any interviews at all (I am talking less that a single interview a week). That was when I decided to stop counting on luck and start doing the best I can. And I am not just talking about getting a job, I am talking about making sure that if the same situation will come up in the future I will be prepered. Those where the times I learned all the principles I wrote in the post.
Looking back I am really thankfull for those times. It really made me better and I can see that in my current job, and thats what I am actually trying say in the post - if you are searching for a job, make the most of it.
Anyway, thanks very much for your comment.
Feb 10, 2010 · Avi Yehuda
Hi Ashish,
As a developer I had 2 periods in my life where I was searching for a new job. The first period was in about the end of 2006 where the software job market was overflowing with open positions. Back than it was much easier to get a job. As you said, no matter how I did in the interview, if my expirience was as they requierd they wanted me almost always. The seconed period of job searching was not too long ago, that was in the middle of 2009, where the software job market was at all time low (at least where I come from). Let me tell you, times were bad. They where hardly any interviews at all (I am talking less that a single interview a week). That was when I decided to stop counting on luck and start doing the best I can. And I am not just talking about getting a job, I am talking about making sure that if the same situation will come up in the future I will be prepered. Those where the times I learned all the principles I wrote in the post.
Looking back I am really thankfull for those times. It really made me better and I can see that in my current job, and thats what I am actually trying say in the post - if you are searching for a job, make the most of it.
Anyway, thanks very much for your comment.
Feb 10, 2010 · Avi Yehuda
Hi Ashish,
As a developer I had 2 periods in my life where I was searching for a new job. The first period was in about the end of 2006 where the software job market was overflowing with open positions. Back than it was much easier to get a job. As you said, no matter how I did in the interview, if my expirience was as they requierd they wanted me almost always. The seconed period of job searching was not too long ago, that was in the middle of 2009, where the software job market was at all time low (at least where I come from). Let me tell you, times were bad. They where hardly any interviews at all (I am talking less that a single interview a week). That was when I decided to stop counting on luck and start doing the best I can. And I am not just talking about getting a job, I am talking about making sure that if the same situation will come up in the future I will be prepered. Those where the times I learned all the principles I wrote in the post.
Looking back I am really thankfull for those times. It really made me better and I can see that in my current job, and thats what I am actually trying say in the post - if you are searching for a job, make the most of it.
Anyway, thanks very much for your comment.
Feb 10, 2010 · Timothy Huertas
Hi Sancar,
Thank you for your comment.
Well the post was already long as it is, I didn't want to overload it with also java riddles, this probably requiers another post, and as you said, it's fun so why not.
I don't know why you said you haven't been asked any java riddles during interviews, I certainly was asked in many of them (not all of them though), perhaps its different in different places.
Feb 10, 2010 · Timothy Huertas
Hi Sancar,
Thank you for your comment.
Well the post was already long as it is, I didn't want to overload it with also java riddles, this probably requiers another post, and as you said, it's fun so why not.
I don't know why you said you haven't been asked any java riddles during interviews, I certainly was asked in many of them (not all of them though), perhaps its different in different places.
Feb 10, 2010 · Avi Yehuda
Hi Sancar,
Thank you for your comment.
Well the post was already long as it is, I didn't want to overload it with also java riddles, this probably requiers another post, and as you said, it's fun so why not.
I don't know why you said you haven't been asked any java riddles during interviews, I certainly was asked in many of them (not all of them though), perhaps its different in different places.
Feb 10, 2010 · Avi Yehuda
Hi Sancar,
Thank you for your comment.
Well the post was already long as it is, I didn't want to overload it with also java riddles, this probably requiers another post, and as you said, it's fun so why not.
I don't know why you said you haven't been asked any java riddles during interviews, I certainly was asked in many of them (not all of them though), perhaps its different in different places.