Relatively similar experience here in Germany. Decided to try a new dentist who immediately told me I had 3 cavities. Went back to my regular who said just 1 cavity and he cleaned it up. I've had an implant done from the same clinic. At least I'm very grateful that the costs were 2-3k EUR. I'm sure US costs would've been much more.
The implant has been life changing. Now I just go in for annual cleaning and am always told to floss regularly. Even here in Germany the dentists can have incentives to give you bad advice, but seems like the US is much worse.
Mostly me exploring how to build a Treiber Stack (first in Go, then in C++) -> Figuring out ABA and Use-After-Free in the C++ implementation, and then touching a bit of Hazard Pointers, and ending with a benchmark comparison b/w a mutex and a lock-free version of the stack.
LLMs are a great tool at teaching and explaining. I don't use it to generate code, but it takes away the pain of searching and setting up dependencies, tools, etc. So I can focus only on the concepts and then do the testing.
It is not perfect, but I learned something that I did not know thanks to these techniques. And that too without reading dense and obscure books. I love it.
You may (or may not) find Paul McKenney's free book on parallel programming interesting - it has an unusual tone for a Computer Science textbook that made it less dry for me. There's a substantial section covering lock free structures.
Why are we so eager to dismiss the very personal experiences of Andrew - someone who envisioned and developed Zig from the ground up? It is entirely within the realm of possibility that what he describes here did transpire. He had bad experiences with one of the more popular projects within the ecosystem - something that he hoped would become successful but the incentives were clearly misaligned.
When in doubt - look at the incentives. And the incentives here are fairly obvious. On one hand we have an open source project that is focused on quality and craftsmanship, and on the other hand we have the world's biggest AI company.
I am not anti-AI. But things like taste and quality matter. And I trust the creator of Zig more than the creator of Bun when it comes to said taste.
> But things like taste and quality matter. And I trust the creator of Zig more than the creator of Bun when it comes to said taste.
Having read both articles I'm in the opposite corner. I found Andrew's personal ad-hominem filled emotional post distasteful and Jarred's purely technical and filled with praise of Zig well written and in good taste.
But it wasn't full of praise for Zig. It specifically pointed out that his project written in zig was full of memory safety bugs, and said that there was no way to get around that if the project stayed with zig. It's ludicrous!
But how is this news? Memory safety bugs are one of (if not the) main source of bugs in C/C++ and also Zig, and Rust's main claim to fame is that it makes it easy to catch these issues at compile time. I feel his criticisms of Zig are fairly uncontroversial.
Memory safety is a source of bugs in languages without garbage collection and/or whatever rust does, however memory safety is not THE source of bugs. If it were then we'd expect code written in JavaScript or Python (memory safe languages) to have zero bugs, and that's definitely NOT the case. When you get the hang of C and C++ memory bugs are not very common compared the normal bugs that all software has. They still can happen but people have gotten the idea that every C program is riddled with them without seeming to realize that code written in C is the foundation for almost everything and has been for a long time. Compilers, operating systems, device drivers, network stacks, core utilities, even games are all written in C or C++ and we are not drowning in killer memory related bugs.
ClickHouse | Distributed Data Infrastructure Engineer | Remote Hiring in the US right now. Seniors/Staff/Principal levels
ClickHouse is a popular, Open-Source OLAP Database. We are ClickHouse Inc, the company behind the database aiming to build the best in class real time data warehouse.
What we are looking for:
Distributed Systems / Cloud Engineers to build
- AutoScaling Systems for a Cloud Database
- A Distributed Caching Layer on top of S3 [0]
If you have experience in productionizing and maintaining distributed systems cloud-based multi-tenant caches - you would fit right in.
We also maintain our own ClickHouse based Data Infrastructure. Bonus points if you've worked on auto-scaling or other data-driven forecasting challenges in the past.
Can work in a fast moving scale-up environment. Proactive and hands on.
You must be independent and self-organized.
Database SRE / Cache Operations experience
Go, Kubernetes, Distributed Systems in general
You will need to be able to do On-Call - debugging production infra, db or cache issues
Low-level database programming (C++, ClickHouse) - This is crucial for the cache.
If you want to work on operating production critical databases/caches in the cloud on or write data-driven algorithms for autoscaling, consider applying! Send me an email: manish.gill [at] clickhouse [dot] com
ClickHouse | Senior Cloud Software Engineer - Distributed Systems / Cloud Databases / Kubernetes | Remote Hiring in the US right now. Seniors/Staff/Principal levels
ClickHouse is a popular, Open-Source OLAP Database. We are ClickHouse Inc, the company behind the database aiming to build the best in class real time data warehouse.
I am hiring for AutoScaling as well as Distributed Cache Production Engineer Roles
What we are looking for:
Distributed Systems / Cloud Engineers to build
- AutoScaling Systems for a Cloud Database
- A Distributed Caching Layer on top of S3 [0]
If you have experience in productionising cloud-based multi-tenant caches - you would fit right in.
We also maintain our own ClickHouse-based Data Infrastructure. Bonus points if you've worked on auto-scaling or other data-driven forecasting challenges in the past.
Can work in a fast moving scale-up environment. Proactive and hands on.
You must be independent and self-organized.
Go, Kubernetes, Distributed Systems in general
You'll need to be able to do On-Call - debugging production infra or db issues
Low-level database programming (C++, ClickHouse) - This is crucial for the cache.
If you want to work on operating production critical databases/caches in the cloud on or write data-driven algorithms for autoscaling, consider applying! Send me an email: manish.gill [at] clickhouse [dot] com
PS: If you're a pure DevOps person or a pure Data Engineer who wrangles data tools, please read the above requirements carefully before firing off an email. This role is an intersection of a lot of sub-roles, not a particular specialization
ClickHouse | Senior Cloud Software Engineer - Distributed Systems / Cloud Databases / Kubernetes | Remote
Hiring in the US right now. Seniors/Staff/Principal levels.
ClickHouse is a popular, Open-Source OLAP Database. We are ClickHouse Inc, the company behind the database aiming to build the best in class real time data warehouse.
What we are looking for:
Distributed Systems / Cloud Engineers to build the AutoScaling Systems for a Cloud Database.
We also maintain our own ClickHouse-based Data Infrastructure. Bonus points if you've worked on auto-scaling or other data-driven forecasting challenges in the past.
Can work in an early stage startup environment. Proactive and hands on.
You must be independent and self-organized.
Good at Go, Kubernetes (Understanding how to manage stateful services in a multi-cloud environment) and Distributed Systems in general.
SQL / ClickHouse SQL (goes without saying)
You'll need to be able to do On-Call - debugging production infra or db issues
If you can do low-level database programming (C++, ClickHouse) that's added bonus.
If you want to work on operating production critical databases in the cloud on k8s + write data-driven algorithms for autoscaling, consider applying! Send me an email: manish.gill [at] clickhouse [dot] com
PS: If you're a pure DevOps person or a pure Data Engineer who wrangles data tools, please read the above requirements carefully before firing off an email. This role is an intersection of a lot of sub-roles, not a particular specialization
Hiring in the US right now. Seniors/Staff/Principal levels.
ClickHouse is a popular, Open-Source OLAP Database. We are ClickHouse Inc, the company behind the database aiming to build the best in class real time data warehouse.
What we are looking for:
Distributed Systems / Cloud Engineers to build the AutoScaling Systems for a Cloud Database.
We also maintain our own ClickHouse-based Data Infrastructure. Bonus points if you've worked on auto-scaling or other data-driven forecasting challenges in the past.
Can work in an early stage startup environment. Proactive and hands on.
You must be independent and self-organized.
Good at Go, Kubernetes (Understanding how to manage stateful services in a multi-cloud environment) and Distributed Systems in general.
SQL / ClickHouse SQL (goes without saying)
You'll need to be able to do On-Call - debugging production infra or db issues
If you can do low-level database programming (C++, ClickHouse) that's added bonus.
If you want to work on operating production critical databases in the cloud on k8s + write data-driven algorithms for autoscaling, consider applying!
Send me an email: manish.gill [at] clickhouse [dot] com
PS: If you're a pure DevOps person or a pure Data Engineer who wrangles data tools, please read the above requirements carefully before firing off an email. This role is an intersection of a lot of sub-roles, not a particular specialization
ClickHouse | Senior Software Engineer - Distributed Systems / Cloud Data Infrastructure / Kubernetes | Remote
US remote preferred right now, EU is technically fine but I'm looking to ramp up in US atm
ClickHouse is a popular, Open-Source OLAP Database. We are ClickHouse Inc, the company behind the database aiming to build the best in class real time data warehouse.
What we are looking for:
Distributed Systems / Cloud Engineers to build the AutoScaling Systems for a Cloud Database.
We also maintain our own ClickHouse-based Data Infrastructure. Bonus points if you've worked on auto-scaling or other data-driven forecasting challenges in the past.
Can work in an early stage startup environment. Proactive and hands on.
You must be independent and self-organised.
Good at Go, Kubernetes (Understanding how to manage stateful services in a multi-cloud environment)
We have a Python service in our Recommendation pipeline, so some ML/Data Science knowledge would be good.
SQL / ClickHouse SQL (goes without saying)
You'll need to be able to do On-Call - debugging production infra or db issues
If you can do low-level database programming (C++, ClickHouse) that's added bonus.
If you want to work on operating production critical databases in the cloud on k8s + write data-driven algorithms for autoscaling, consider applying!
Send me an email: manish.gill [at] clickhouse [dot] com
PS: If you're a pure DevOps person or a pure Data Engineer who wrangles data tools, please read the above requirements carefully before firing off an email. This role is an intersection of a lot of sub-roles, not a particular specialization.
The implant has been life changing. Now I just go in for annual cleaning and am always told to floss regularly. Even here in Germany the dentists can have incentives to give you bad advice, but seems like the US is much worse.
reply