umut

Yes, very true.. But you just don't need to maintain the exploding specificity hell, instead use a declarative workflow, which is significantly easier to reason about.

A viable alternative to all this is using tailwind, can't recommend it highly enough. When you pass the initial period where you feel like you're repeating yourself (1h max) it takes the nervousness out of your CSSing, it feels more like coding and less like schmoozing..

Just a happy user

I think you might be underestimating the fact that your marketing copy is a good proxy for your product commitment in the long run. I am having difficulties adding you to the short list of "platforms to be considered when starting out a new project" mainly for this reason alone..

Best of luck though, i just wanted to give honest feedback

I second this rather strongly.. The harder it gets to "stop" and clean-up shit, the quicker it gets to just lose it.. Especially relevant in environments where the authors of the write-only codebase are not around anymore. Somehow it is hard to blame/hate someone you go out with for lunch or beers.

What really worked great for my teams in the past is to game the transition so that the team as a whole sees it as an internalized mission, usually much stronger than that of the company. Then killing X lines of code from the old mess and beautifying the codebase becomes a shared and extremely satisfying exercise

I think your best bet is to find someone

- who thinks (s)he can generate $3k/mo (essentially 2x of your target),

- who has reasonable proof that this is plausible and

- who cannot build it (her/him)self.

It is also great to have company, to keep you on track, motivate each other when you need it (and you will), and help you sell.. Don't take this as a freelancer gig, make sure you are cofounders/partners in this

Best of luck for whatever life throws at you! Cheers

Great business idea: time-shared schooling across two locations.. Spring/summer in northern places and winter in south where it is warmer, without disrupting children's schooling and social lives.. Sort of like two home families, it would dramatically improve lives of families who can afford it.

Really hope that our societies can fund some research and development to bring elasticity to health care capacity. This won't be the last time we as humans will need it, and it will help if some smart people work on this instead of ad click optimization..

This has no more value than being a "fun fact" (sorry for the word 'fun' in the context of a pandemic and death numbers).. a) it is something you don't have any control b) the diff (odds, bayes factor or any similar definition) is not that great to have an effect on public policy (something like, let's focus our resources on region A, since region B has less risk kind of change)

So, let's all enjoy this study as food for our curiosity, and move on with all the usual measures of social distancing, extra hygiene control and all.. Especially dangerous, if even one crazy person goes out because he has a certain blood type and helps the disease spread

looks very unfinished to me, am i missing something?

Upvote a million times!

A simplified configuration flow sounds too dangerous to me. IMHO, making it easier to "configure" is not necessarily a good thing, and in this particular context, is THE source of a ton of software development bad practices, low SNR and micromanagement.. </rant>

or maybe someone who has a certain degree of "excessively" in their "pedantic"

So recursive :)

Congrats! Great problem to solve, would you mind sharing some architectural decisions or technical details about how you plan to tackle scalability?

You can try Truecaller (www.truecaller.com). This is one of the essential problems we are addressing and it works quite well for +200 million users worldwide..

app users downloading the app from relevant appstores (plus some minor set of users logging in on our website with social login providers)

www.truecaller.com Because 250M users!

It would be cool if someone does an A/B testing over a significantly big population of users and show us the dropoffs on each version. I would love to have no password login (temp token), but if the users don't receive them on time (email deliverability might be laggy at times), or they don't get the idea, or they don't care/like the method.. Well, you got my point.

I dont agree that you can kill me. At least cut a few fingers off, before killing. ^^ No, not this

Sometimes zero downtime migrations are not worth the effort. In most of the cases, you end up thinking of a 3-state picture (BEFORE / DURING / AFTER) and the delta between DURING and AFTER needs some manual work. As long as you don't drop data or end up with irreversible changes, you manage the process and complete the migration just fine.

He lost me at "But Kris, our business coach, pushed us to try it."...

Definitely Dropwizard or Ninjaframework

We use JDBI @Truecaller together with Metrics library. Not only it is clean and tidy, it also gives you immediate profiling around your database calls. This is priceless in a big service oriented environment. With it, you can exactly see the rate of happening (mean/last 1/5/15 minutes average) and latency (mean/avg/std-dev/75/95/98/99/99,9percentiles) for each database query. I wouldn't want to go back to manual logging and optimization hell. JDBI+Metrics opens a totally new dimension to your monitoring/profiling/optimization!

Yes it is just a binding between Jersey and templating engines (they maintain two of them: mustache.java and freemarker. I strongly recommend freemarker, since it is more complete in UI related transformations. This way it lets your Model layer to stay clean. But if you need something exotic, you can bind to your templating engine of choice easily)

Jetty is up to date, but Jersey is old yes. But the new jersey is also a bit problematic, more stuffy and slow (from the benchmarks of others, I haven't done it myself). But the good thing is, there is a big and passionate contributor community around dropwizard (check their github/google groups) and this means if the new versions of libraries are worth updating, they get in pretty quickly.

Couldn't agree more.. But this comes with the most cliche discussion with a smartass looking at your code. Dude, I know what getters and setters are, I just don't agree

I can strongly recommend Dropwizard for the plan. It is much less stuffy/enterprisy and you can easily split big apps into smaller services. It is some glue code on top of Jersey run in embedded mode Jetty (thus very little ops work needed). Play Framework is also nice, but a bit too much opinionated! Meaning hard to make it do something in another way, which happens in real world big applications...

what is this obsession with teaching your kids how to program? I would not want my future kids do the same always worrying occupation that I do... probably the world as well as programming will be totally different then anyways. Just teach him/her some analytical thinking through 100 year old games and let the evolution play his part. There is no such thing as full control of your kid's destiny, just forget about it already...

In a world where twenty-something founders are highly praised, can this be really reflected on the startup scene? Me being 33 now, I feel like I can achieve much more with much less resource now. I am not sure if this is just an illusion or truth, maybe I can write back in ten years and see if I am right on this one...

Game companies are all the way in for bait-and-sell IAP model. In other words push some pain intermittently and then try to sell the painkillers. Which seems to work for them at least for now. I wish we would have a more healthy model to cover the production+marketing costs, but it's not gonna change anytime soon...

For apps with more utility, still there is a chance to go for upfront payments, but then again significantly slowing down user traction especially when there are free alternatives (even if they are not any good)

And there is the ad-supported model, which boils down to how much traffic your app generates, from which countries and how engaging your app is. A reaaalllly long shot for all the apps except for a lucky few