Do you want to make it open source? :)

Maybe. I don't see any reason not to!

Edit: I can't reply to any other comments at the moment due to low karma. In response to wrinkl3 and others, I will likely be sharing more details about the development process and network in the next week or two, probably at eigenloss.party.

Berlin is way better than Dubai. Berlin has more atmosphere and is not that "american" like Dubai. Berlin has a big developer scene and millions of startups and meetups. But remember, weather is not that nice in Germany :D

What a time to be alive! :D

"Error establishing a database connection"

This is also what I learnt as a programmer.

I think IT and especially open source is one area, where your gender, background, sexual orientation doesn't matter. The most open source projects I'm using or working on, are made by people I don't know how they look. The only thing that matters is the ability of writing good code.

The author is in that point right, that there are more male programmers than female. But to solve this problem you have to start way earlier, with getting the interest to tech things of a child (regardless of gender) in school or even earlier.

Major open source projects are disproportionately managed and staffed by people with full-time jobs at major software companies, and the process of obtaining and thriving in one of those jobs is not intrinsically color and gender blind, so this argument isn't persuasive.

> process of obtaining and thriving in one of those jobs is not intrinsically color and gender blind

So it's ok now to post a comment with a strong statement without any data?

> Major open source projects are disproportionately managed and staffed by people with full-time jobs at major software companies, and the process of obtaining and thriving in one of those jobs is not intrinsically color and gender blind, so this argument isn't persuasive.

How is it surprising that they work in software? It's like finding out that your welding instructor has worked as a welder; surely somebody who contributes to a field in public is more likely to have a job in that field in private, but does that mean that not having a job precludes you from having a skill?

I mean, I've been NEET going on half a year, and I'm contributing to open source projects, do I need a software job to do open source? I was contributing to open source projects before I was ever employed, do I need to have had a job to do open source?

I always wonder, why IT companies don't test their backups? Even if it's the prod db, it should be tested on a regular base. No blame to the dev.

You can become programming teacher for startups in Gaza.

Check out: https://gazaskygeeks.com/

Kotlin - The Source Awakens

Haha this one is even better.

> They said in most cases it doesn’t make a big difference… unless you use the REST API.

So in the end it was a coding problem, because you forgot to add Keep-Alive = true? If you use the provided SDK's it should be no problem then right?

I don't think Keep-Alive = true would be enough. The article also mentions TLS session tickets would be necessary.

And it's hard to call this a coding problem if the requirements of the API never specified that session tickets and keep alive were necessary.

With keep-alive you may not even need TLS session tickets (if the keep alive timeout is long enough).

keep-alive keeps the HTTP/TLS socket open.

TLS session tickets allow to close and "cheaply" reopen TLS session on a new socket for a new HTTP connection.

Using both keep-alive and TLS session tickets is optimal.

Yeah it's no coding problem on purpose, but sth you could actually fix. But it's not good manner to not mention it from Firebase.

It's absolutely good manners for Firebase to tell you "If you fix this thing, your costs will go down."

> It's absolutely good manners for Firebase to tell you "If you fix this thing, your costs will go down."

I wonder how many HN startup founders go around telling their customers on how to pay less.