aamederen

It's funny that, "GROUP BY ALL" makes a lot of sense but it had never crossed my mind before!

For a more baby-steps approach to resiliency, one might start running software on less-virtualized computers, creating a small home-lab, running software on bare-metal hardware that you actually own.

Related story without the paywall: https://www.bbc.com/news/articles/cx279v4z9lzo

I feel mixed about a violance game being one of the top points in computing technology.

It makes the most sense (to me) for app platforms like Firebase to invest deeply in the AI application development wave. Creating something from scratch with prompts is impressive but the gap between something that works locally to something that people can use is still large enough to require some dev & ops expertise.

This is cool. A next step could be to have a single AI-powered tool to call these tools, maybe in a more deterministic way than new-gen AI agents.

Even though the aim here is different, sustainability through repair and reuse is uplifting. It's also a reminder that 10-year-old computers can do a lot and most of us may not need the latest shiny laptops.

Congratulations! I'm happy to see the PostgreSQL license.

You can run Citus on EC2 for now.

I agree with the team-size aspect, but the age argument won't always hold.

Junior folks bring their own energy, flexibility, hunger for learning and the resilience to unclear future. As folks get more mature, growing egos, stability expectations, tendency to settle down can get in the way.

Overall, this boils down to the fact that teams and people are not just head counts and there's a factor of chemistry need to be considered depending on the culture, founders, geography and the business itself.

Thanks for creating this content, this looks pretty good and it was a good time for me to refresh my basics about computer networks.

I tried checking the content with my kindle (a Kindle Touch paperwhite 6 inches) and the first chapter rendered pretty good, with images and text aligning as intended. However the second chapter did not render the first figure and beyond. Chapter 3 rendered OK, similar to Ch 1.

A few more feedback if that helps for enhancing the format even more: - Colors, and references to those do not work on a kindle. I only saw one minor use of colors (red, green) in Chapter 1 so that's not a blocker. - For some reason, the kindle browser doesn't put left and right margins on the page, so the text uses the full length of the device. - Links are rendered with a pale gray, sometimes hard to distinguish. - Figuring out why the Chapter 2 did not render would definitely help.

a shittier version is https://bitfission.com/

Workflowy, alongside a regular email and calendar. Workflowy is very simple yet flexible and has the tools that make me operate without thinking much.

It allows me to quickly keep a GTD-ish list of stuff going on and action items needs to be taken and I can organize them as detailed as needed with labels, colors, etc. I find the simplicity/features ratio work well for me.

Getting Things Done method by David Allen

tl;dr; We are lazy, so if a process gets simpler/faster/easier, we tend to use it more often.

Here's a story about why you are right to be anxious: https://hackernoon.com/how-we-spent-30k-usd-in-firebase-in-l...

AFAIK, PaaS solutions like heroku have a similar way of working, at least for side-projects. Here, you deploy a container and Google runs it somewhere and Heroku containerizes your application every time you push it. Similar to here, Heroku's free hobby containers also go to sleep in ~30min inactivity.

Basics of presentation skills like

- Using voice, body and mimics properly

- Not putting lots of text on slides and just reading them

- Using bullets instead of paragraphs

- Tell a story and use a less formal more friendly style (not always but applies to majority of technical presentations)

A nice video about the topic: https://www.youtube.com/watch?v=vB2pl1QbY3I

I work at Citus (now Microsoft) so my opinion is biased but I think Citus [1] codebase is a really good example.

It borrows all the best practices from PostgreSQL the naming of variables and functions are more self-explaining in general.

I also believe that the practices around PRs and code reviews are also good examples.

[1] https://github.com/citusdata/citus

As an outsider, my initial reaction is "does every new database system have to come up with their own SQL-like language?"

As a first time visitor, I find the design very clear and readable.

As a user, instead of the "we will send the data once you are online" message, I would prefer "you seem offline, please try again once you are online" kind of approach. I would not like to rely on a background worker on a mobile device and I would not know whether my form has been sent, a timeout occured, what happens if I refresh the tab, what happens in a poor connection (seems online but can't connect to internet). Therefore, I would like to be just notified about the connection issue and try again once I got out of the metro.

I believe we are going to see services that will subscribe to all streaming facilities for you (preferably with a discount) and serve content from various studios from a unified interface. Then, we can have the same problem for these "streaming service subscription services". Sad.

Firebase taught me, for a B2B2C kind of app:

1) Relational databases are more flexible: you model your data according to the actual "relations" between them, instead of how you want to query them. This makes it easier to add new views/queries to your application.

2) Joins are necessary

3) In a very short time, you need complex authentication logic and it is very hard to do it without looking at the requested (and related) data directly. Best way to do this is a good-old rdbms + server app

4) Moving more logic from servers to clients forces you to be more careful about client versions, duplicate logic among different clients (iOS, Android, Web, Dashboard)

Popular, intelligent, charismatic CEO: Check Stylish, pricy, premium product: Check Fanboys and Haters: In Progress...

Is it possible to do more complex requests in GraphQL, like getting the favorite venues of people that favored "Garaje" or is it left to the API provider?

Can this technique be used for recognizing handwriting of individuals?

I had a strange internship topics involving Ada. I tried to run a huge program (a simple stdio wrapper around a huge library actually) on an Android machine (Android 2.3, ARM). At that time, the only ADA compiler for ARM was available on BSD so I had used a Windows machine for development and a OpenBSD laptop for compiling the wrapper.

The subtyping feature I love the most. You see the benefit when you need to call a function which is taking many numeric arguments, all of them is a subtype so you can't give the arguments in the wrong order (latitude and longitude for example).

Why not use something like Google Slides and try to make it via md?

If it is so important to be able to find the pitch of a github repo, just put the link in README.md.

I see it becoming Github for container house manufacturers. Put some "community" level designs here to market yourself and your "enterprise" level designs or finished products.

I believe, from time to time, you just need to stop developing new stuff for a period of time and dedicate the team to improve the overall quality, pay technical depts, hunt bugs, remove legacy code and refactor still existing ones.