umut

"transfer of knowledge" being extremely hard when the requirements and projects have no structured documentation. Faster in short-term, but obviously creates technical debt in the long-term...

Regardless of who is playing the 'game of crossing the border' it should provide super low iteration times. Otherwise it is counterproductive.

I am a coder, I can photoshop too, if needed. But it would probably kill my rhythm to find a base psd file, change something and then produce intermediate assets, then deploy then see the difference. That's why html/css is a step forward... Likewise, if you are designing and somehow want to change the behaviors, it should be as easy as that. That's the beauty of scrappy development environments...

Congrats, looks really nice! (already forwarded to our testing team)

If you add a 'proxy layer' to your solution, that would be awesome. To explain the scenario, it is really very valuable for us app startups to see how it behaves in China, in India, in Europe, in US etc. You may keep your current system intact, and 'if' the customer desires so, you can route your connection over those proxies(from real ISS'es) from all over the world and test it 'as if...' This is really important and not so hard to implement... But sometimes, you can catch bugs and usability horrors with slow or dropped connection or some weird proxy mambo jambo played by ISS providers.

Email delivery is almost commodity nowadays, This is what stands out (on top of a respectable quality of service of course)

a good book advice plus a nice smile on my face... thanks!

of course bootstrap et al are the first place to go, but i was referring to one step further in design. Like custom look and feel, some marketing material, nice typography, infographics, nice app UI/UX design (visuals, effects etc)...

I know good stuff when i see them, but don't know how i can create them. The real problem is i cannot figure out my way to gradually improve my skillset and get there. :( That is actually my problem and the reason why i asked the question in the first place.

But thanks for the answer anyway... Cheers!

The biggest success in our story involves perseverance and being humble. Any startup involves ups and downs, so especially the early recruits should be there to lift the heavy weight when needed. Losing an employee is bad for any company, but it is more relevant and can be severe when you are a small startup, since most roles don't have substitution scenarios, yet.

Being humble is also crucial, coz when you are very few, keeping the database up and putting out the garbage may sometimes be equally important.

Seen this may times now, and most of these efforts end up in something slightly better than the mess you started with. I believe the main reason is lack of support, mostly political. This has nothing to do in particular with Java or any other technology, it is just lack of direction...

the buttons on the left side and bottom row means maximum stretch for the most common right hand thumb using crowd. Maximum stretch may be translating to maximum pressure. Just a wild guess...

37 signals has a similar experiment,

"Back in 2008 we shared some of our workplace experiments including the four day work week (still in effect May – Oct), ...." mentioned at: http://37signals.com/svn/posts/3186-workplace-experiments-a-...

and the 2008 article: http://37signals.com/svn/posts/893-workplace-experiments

actually i have been developing a pretty advanced app with more than a million downloads... the main reason for me to ask was, if any company is brave enough to show what's running under the hood... It could be a good exercise for companies like Twitter to show everything.

perfect reply, definitely agree with the points stated...

For a scrappy startup, it may not mean much since it is verbose and idioms are a bit ugly-ish at first.

But as startups grow into real businesses, the developer productivity and maintainability versus performance makes Java one of the best options available today. JVM is really one good piece of software and against all the preconceptions, java is a really nice language to build large scale systems...

// been a java developer for around 10 years, and any other language i have used (a lot of them) disappointed me in one way (productivity) or another (performance)

No one, actually it's the character limit for the title. :) I didnt mean to be hostile or disrespectful. I just believe that they need some more time in the evolution process, make the app better and then ask for feedback, which at that time more likely to produce more meaningful feedback from the community...

I am actually, the issue here is not that i don't like these projects, but i cannot give meaningful feedback on them... When you develop any sufficiently big project, most of the assumptions and specifications change over time. This is evolution. And what i criticise is, whether it is a good idea to show a half-baked app and make people think that it is useless. I believe waiting a bit more and developing the app and then posting it makes more sense. For all the learning practices, i agree it is very valuable experience, but just let them evolve...

Don't get me wrong, the title is put together because of the character limit. I truly appreciate and like the idea of putting together bootstrapped apps, i work for one of those ideas going into maturity, but then don't you think you lose one silver bullet you have. Other people's feedback is important, especially on HN, so i was thinking of using it wisely and show them a developed feature-set, at least some level of maturity. I am sure, twitter's thing is not the idea of micro blogging and following and such, but rather the feature set they have put together and served and scaled for the long time they are alive. Otherwise competition would crush them, remember Google Buzz...

well, my intention was asking why such small things, i think mvp is overrated, people can put together a meaningful set of features and produce a real product, probably not in a weekend but in a month or two or six... then it makes more sense for the audience to check the featureset and give more meaningful feedback. That's my opinion at least. Don't get me wrong, i appreciate and support all the efforts by these bright people, but...

This could be the big step for the developers' dream of using the actual target device as the host for developing(end-to-end toolchain and the debugging host of course). Success of open systems(both HW and SW) comes from this marginal-looking(huge in fact) idea. So, the hardware is there, but unfortunately they lack the determination. It is sad to see Apple performing even worse than MS on this very department.

I personally will insist on "not" buying any Apple product unless they develop a strategy to innovate(as they did in the past) instead of trying to monopolize the scene...