b-man

I think your post misses the point of the DBMS centralization: managed consistency.

It is not about ops cost in infrastructure, but ops cost in debugging consistency errors.

b-man

10 日前議論

  Location: Brazil (UTC-3, overlaps US hours)
  Remote: Yes
  Willing to Relocate: Yes (US preferred)
  Technologies: SQL Server, DBT, SQL Mesh, PostgreSQL, SQL, OLTP & OLAP, cloud optimization, query optimization, large-table migrations, F#, Clojure, Python, C#, C, Java, Ruby, Rust, Prolog, OCaml, Haskell
  Email: ebellani at gmail

I specialize in rescuing and scaling PostgreSQL systems that have become bottlenecks due to schema debt, growth, or operational complexity. Recent work: re-architected two multi-terabyte OLTP tables (~2TB and ~1TB) handling 200+ writes/sec, improving scalability and reducing application-level complexity.

My work focuses on high-risk database migrations, dangerous schema remediation, hot-path optimization, and making existing systems scale without rewriting the product.

Open to consulting or full-time roles where data is central and performance matters.

b-man

28 日前議論

  Location: Brazil (UTC-3, overlaps US hours)
  Remote: Yes
  Willing to Relocate: Yes (US preferred)
  Technologies: SQL Server, DBT, SQL Mesh, PostgreSQL, SQL, OLTP & OLAP, cloud optimization, query optimization, large-table migrations, F#, Clojure, Python, C#, C, Java, Ruby, Rust, Prolog, OCaml, Haskell
  Email: ebellani at gmail

I specialize in rescuing and scaling PostgreSQL systems that have become bottlenecks due to schema debt, growth, or operational complexity.

Recent work: re-architected two multi-terabyte OLTP tables (~2TB and ~1TB) handling 200+ writes/sec, improving scalability and reducing application-level complexity.

My work focuses on high-risk database migrations, dangerous schema remediation, hot-path optimization, and making existing systems scale without rewriting the product.

Open to consulting or full-time roles where data is central and performance matters.

b-man

先月議論

https://fred.stlouisfed.org/graph/?g=1WPjJ

b-man

2 か月前議論

have you tried just using emacs? They have an emacs mode https://github.com/coalton-lang/coalton-labs

b-man

2 か月前議論

Great refs. I think one can find more accessible sources for this knowledge, for instance this course:

https://www.youtube.com/playlist?list=PLoYRQl2t0w0EjRIb9Jr1y...

or Feser's articles such as

- https://www.firstthings.com/article/2013/04/kurzweils-phanta...

- https://edwardfeser.blogspot.com/2019/03/artificial-intellig...

b-man

3 か月前議論

> The Agile example makes this worse, not better. Yes, Agile was overhyped and badly implemented in many places. But using that to indict the entire movement as Girardian ritual is precisely the logical move the author claims to be critiquing: take some real failures, blame them on a paradigm rather than specific implementations, declare the whole thing rotten. He scapegoats Agile to validate his theory about scapegoating

I don't think the author did that at all. He was fair to interactive development. He specifically points out the scapegoating of waterfall, where the methodology was misrepresented in order to create the space for agile.

b-man

3 か月前議論

fwiw, your career page seems broken (https://supabase.com/careers)

b-man

3 か月前議論

   Location: EST
   Remote: Yes 
   Willing to relocate: Yes (US preferred)
   Technologies: PostgreSQL (partitioning, performance, OLTP architecture), SQL, F#, C#, C, Java, Clojure, Common Lisp, Scheme, Emacs Lisp, Python, Ruby, AWS, Linux
   Email: ebellani at gmail

I work on high-throughput systems, especially when they’ve grown into a state where migrations, performance, or schema design have become limiting factors.

Recent work:

Re-architected two multi-terabyte OLTP tables (~2TB and ~1TB) receiving 200+ writes/sec. I focus on “rescue architecture” work: fixing dangerous schemas, stabilizing hot paths, removing app-level complexity, and making Postgres scale without rewriting the product.

Open to consulting or full-time roles where data is core to the business and performance/architecture matters.

Résumé: https://www.linkedin.com/in/eduardo-bellani/ https://ebellani.github.io/

b-man

4 か月前議論

ocation: EST Remote: Yes Willing to relocate: Yes (US preferred) Technologies: PostgreSQL (partitioning, performance, OLTP architecture), SQL, F#, C#, C, Java, Clojure, Common Lisp, Scheme, Emacs Lisp, Python, Ruby, AWS, Linux

Email: ebellani at gmail

I work on high-throughput PostgreSQL systems, especially when they’ve grown into a state where migrations, performance, or schema design have become limiting factors.

Recent work:

Re-architected two multi-terabyte OLTP tables (~2TB and ~1TB) receiving 200+ writes/sec. I focus on “rescue architecture” work: fixing dangerous schemas, stabilizing hot paths, removing app-level complexity, and making Postgres scale without rewriting the product.

Open to consulting or full-time roles where Postgres is core to the business and performance/architecture matters.

Résumé: https://www.linkedin.com/in/eduardo-bellani/ https://ebellani.github.io/

b-man

5 か月前議論

Location: EST Remote: Yes Willing to relocate: Yes (US preferred)

Technologies: PostgreSQL (partitioning, performance, OLTP architecture), SQL, F#, C#, C, Java, Clojure, Common Lisp, Scheme, Emacs Lisp, Python, Ruby, AWS, Linux

Email: ebellani at gmail

I work on high-throughput PostgreSQL systems, especially when they’ve grown into a state where migrations, performance, or schema design have become limiting factors.

Recent work:

Re-architected two multi-terabyte OLTP tables (~2TB and ~1TB) receiving 200+ writes/sec. I focus on “rescue architecture” work: fixing dangerous schemas, stabilizing hot paths, removing app-level complexity, and making Postgres scale without rewriting the product.

Open to consulting or full-time roles where Postgres is core to the business and performance/architecture matters.

Résumé: https://www.linkedin.com/in/eduardo-bellani/ https://ebellani.github.io/

b-man

6 か月前議論

> This is the reason for the push-back against it.

Do you have evidence for that? From memory, it was basically because it was associated with the java/.net bloat from the early 2000s. Then ruby on rails came.

b-man

6 か月前議論

Location: EST Remote: Yes

Willing to relocate: Yes (US preferred)

Technologies: PostgreSQL (partitioning, performance, OLTP architecture), SQL, F#, C#, C, Java, Clojure, Common Lisp, Scheme, Emacs Lisp, Python, Ruby, AWS, Linux

Email: ebellani at gmail

I work on high-throughput PostgreSQL systems, especially when they’ve grown into a state where migrations, performance, or schema design have become limiting factors.

Recent work:

Re-architected two multi-terabyte OLTP tables (~2TB and ~1TB) receiving 200+ writes/sec. I focus on “rescue architecture” work: fixing dangerous schemas, stabilizing hot paths, removing app-level complexity, and making Postgres scale without rewriting the product.

Open to consulting or full-time roles where Postgres is core to the business and performance/architecture matters.

Résumé: https://www.linkedin.com/in/eduardo-bellani/ https://ebellani.github.io/

b-man

7 か月前議論

I have written the entire backend of a fintech using nothing but postgresql, integration over http and webhook receival included (the last bit was with postgrest, but you get the point)

b-man

7 か月前議論

Location: EST

Remote: Yes

Willing to relocate: Yes (US preferred)

Technologies: PostgreSQL (partitioning, performance, OLTP architecture), SQL, F#, C#, C, Java, Clojure, Common Lisp, Scheme, Emacs Lisp, Python, Ruby, AWS, Linux

Email: ebellani at gmail

I work on high-throughput PostgreSQL systems, especially when they’ve grown into a state where migrations, performance, or schema design have become limiting factors.

Recent work:

Re-architected two multi-terabyte OLTP tables (~2TB and ~1TB) receiving 200+ writes/sec. I focus on “rescue architecture” work: fixing dangerous schemas, stabilizing hot paths, removing app-level complexity, and making Postgres scale without rewriting the product.

Open to consulting or full-time roles where Postgres is core to the business and performance/architecture matters.

Résumé: https://www.linkedin.com/in/eduardo-bellani/ https://ebellani.github.io/

b-man

7 か月前議論

> Not to mention that perfectly normalizing a database always incurs join overhead that limits horizontal scalability. In fact, denormalization is required to achieve scale (with a trade-off).

This is just not true, at least not in general. Inserting on a normalized design is usually faster, due to smaller index sizes, fewer indexes and fitting more rows per page.

b-man

8 か月前議論

fixed

b-man

8 か月前議論

Indeed. I was trying to make that point on my concluding paragraph.

b-man

8 か月前議論

> That may be. What's not specified there is the immense, immense cost of driving a dev org on those terms

I'm happy that we agree on the solution, but disagree only if it is cost worthy. About the cost, I took that into consideration when I wrote the conclusion:

> FAANG-style companies are unlikely to adopt formal methods or relational rigor wholesale. But for their most critical systems, they should. It’s the only way to make failures like this impossible by design, rather than just less likely.

There is an actionable plan in the article. It is possible to run teams like these. It is an economical decision of upper management to run the risk of having these outages vis-a-vis this alternative.

b-man

8 か月前議論

a fully normalized relation is one where the SQL (say) table in question represents one and only one predicate of your business rules.

It is literally impossible for that to be done automatically. Someone needs to look at the resulting code and confirm that that was the case.

投稿

Why Zulip? Efficient communication with organized team chat

What Nobody Explains About Debezium in 2026 (But Should)

Do you need separate systems when you already have Postgres?

AI boom risks global financial crash, warn central bankers

All you need is PostgreSQL

Recruitment and Selection of high performing programmers

Throwing 107 GB and 5B fake rows of order data at DuckDB and Athena

Does AI Adoption Improve Productivity? Effects over the First Three Years

The Rise of Single-Node Processing: Challenging the Distributed-First Mindset

Stretching a point: the economics of elastic infrastructure

Watch These Judges Rip into Lawyers for Citing Cases That Don't Exist

Writing vs. Shipping: Productivity Effects Across Generations of AI Coding Tools

Do we fear the serializable isolation level more than we fear subtle bugs (2024)

Software Development Job Postings are going up in the last year

6M Fake GitHub Stars: How to Vet Open-Source AI Tools

Coalton is an efficient, statically typed Lisp with ideas from Haskell and OCaml

The uncritical adoption of AI in science is alarming – We need guard rails

State of Code Developer Survey report [pdf]

Hallucinated citations are polluting the scientific literature. What can be done

An Aristotelian understanding of object-oriented programming

コメント