HNHacker News
TopNewBestAskShowJobs

zacksiri

259 karma · joined January 11, 2022

agentic movie database - https://memovee.com blog - https://zacksiri.dev
submissionscomments
zacksiri··on Transformers Can Do Arithmetic with the Right Embeddings
I think the problem here is that 'understanding' is not the same as curve fitting.

If all one is doing is giving a model lots of data and fitting curves it's not really 'understanding' but brute forcing it's way (with gradient descent) and then storing the weights and finally approximate the solution when a query is passed in.

This is not the same as understanding. Human intelligence can operate deterministically as well as non-deterministically. We can listen to language, which is by it's nature non-deterministic and convert that into deterministic operations and vice a versa. IE we can operate on some logic and explain it in multiple ways to other people.

Understanding requires much less data than brute forcing your way into pattern recognition.

When you see a simple number like this 2 * 4 you are able to understand that it's equivalent to 2 + 2 + 2 + 2 and that in turn means 1 + 1 + 1 + 1 + 1 + 1 + 1 + 1 <- Count that and you've got your answer.

Because you 'understand' this basic concept and all the operations in between you are able to compute more examples. But you only need to understand it once. Once you understand multiplications and additions and all the tricks in between you are able to compute 23 * 10 without being fed 23 * 10 as prior data. Understanding is very different from fitting a curve. You can reach conclusions and understanding through pattern recognition, but it's important to differentiate 'approximation' from 'calculation'. If you understand something in it's entirety you should be able to calculate an outcome deterministically.

Right now LLMs lack 'understanding', and seems to only 'approximate' which may seem like 'understanding' but is actually not.

zacksiri··on Bend: a high-level language that runs on GPUs (via HVM2)
What would be super interesting is having something library, and able to use something like this inside Elixir or Ruby, to optimize hotspots.
zacksiri··on Show HN: Open-sourced LXD / Incus image server
Here’s a blog post that goes into the story of what happened and has more links. Would love feedback on the project and what people would like to see in the future.

- https://opsmaru.com/blog/open-sourced-lxd-incus-image-server

- https://github.com/upmaru/polar

- https://github.com/upmaru/icepak (github action)

- https://images.opsmaru.com

zacksiri··on Nvidia Unveils Blackwell, Its Next GPU
They might re-purpose the G to Generative

Generative Processing Unit works for all cases.

zacksiri··on Astro 4.3
I love astro, coincidentally enough we just enabled astro deployments on our platform engine https://opsmaru.com/docs/application/astro/static/

Our docs is also built with Astro starlight.

zacksiri··on AWS cancels serverless Postgres service that scales to zero
There is a good alternative, https://neon.tech check them out. Really good bunch. Product is great and it's open-sourced https://github.com/neondatabase/neon
zacksiri··on Sticking to 8192 signatures per slot post-SSF: how and why
> A purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another without going through a financial institution.

Depends on how you read this, but to me, this is a replacement for fiat, I should be able to pay my butcher / baker, that hasn't happened yet. If i walk to a merchant near my house they will all reject crypto in any form.

zacksiri··on Sticking to 8192 signatures per slot post-SSF: how and why
Thailand
zacksiri··on Sticking to 8192 signatures per slot post-SSF: how and why
I feel like crypto in general was designed by speculation, and not real use-case.

If you read the original bitcoin whitepaper we have veered into a completely different direction.

I was fortunate enough to build and operate a payment system, during covid 2019 - 2022. It was able to do everything required to process payment maintain an accurate ledger. Our little team of 6 built it in 9 months.

It was centralized yes, and that made things a lot simpler than crypto so comparing it to crypto is a bit unfair admittedly. But you know the difference is it was designed based on real use-case. It could process billions of $ in transactions. Could scale up / down etc...

More importantly we had real people using the thing. People who had no idea how payment systems worked. People were sending money to their mothers for her birthday. Sending money to pay for school fees, hospital bills, etc...

What the crypto community including Vitalik Buterin has failed to realize is the nodes on the network (nodes accepting any given currency) is everything. The regulators have done a very good job of keeping crypto's contained within just 'speculation'. I feel the window of opportunity for it to spread has been shut (for now), mostly by the crypto community themselves with all the fraud and lack of any improvements in UX this long into the game.

While the crypto developers will happily hack away and fabricate use cases based on speculation, and refuse to reduce friction / fees and improve UX. Crypto in it's current form is dead, something new will arise with all the learnings of the current-generation crypto. As much as I believe in the mission of crypto. I'm confident that this proposal like all the other proposals refuse to acknowledge the problem with ethereum and any other crypto, which is I still can't buy bread with it. This proposal is another evidence to show that they're simply focused on the wrong set of problems.

Edit: Update team size mentioned above from 4 - 6 for accuracy.

zacksiri··on De-crufted Windows 11 coming to Europe soon
This is one of the marks of good product managers. Cut the cruft from the product. It's refreshing that in this case regulators are cutting things from the product rather than enforcing things to be added like cookie banners.
zacksiri··on A coder considers the waning days of the craft
I think it depends on what you do, if you are doing repetitive work between projects, you're going to find that yes GPT can do most of the work you're doing. However if you're creating new systems, with multiple components and parts. You're going to find that GPT is not that much help.

I pay for GPT-4 and Github Copilot, all I can say is when I'm trying to do repetitive work like writing tests, copilot swoops in and gives me 'mostly' working code. But when I go in to the real creative stuff, that needs real thought and is non-obvious, I don't get much help from copilot it either just doesn't suggest anything or suggests completely the wrong thing.

I think at least for me, the comparison I would use is, construction work. There are many different kinds of constructions, anything simple from making ikea furniture to building bridges. If the coding you do is the equivalent of making ikea furniture. Then yes that stuff is going away, because it's going to be replaced by machines that can produce those parts in bulk.

But if you're creating something special like the Burj Khalifa, or the Golden gate bridge equivalent but in code, no AI is not going to do that for you. It can help with some parts, but no way AI is going to do that sort of engineering, at least not in it's current state.

I think it's worth noting "Coding" spans so many kinds of systems and scale. Not all coding work is the same. Even if you're talking about things which are well-known like "e-commerce" in that industry there are so many variations / many different scales / many different ways to look at the problem.

zacksiri··on California slams San Francisco for 'egregious' barriers to housing construction
Archive link: https://archive.is/QWY6V
zacksiri··on Choose Postgres queue technology
The job queue had it's own table. It's basically whatever was the default of the job queue library we were using.
zacksiri··on Choose Postgres queue technology
Yes, one of the theory was that the index wasn't the problem because there was already a multi column index on that particular column. However the PG analyze tool showed some particular query didn't utilize the index, so there needed to be a separate index just for that particular column.
zacksiri··on Choose Postgres queue technology
Yeah, I think though what happened in this scenario probably happens a lot everywhere else also. In my entire career, this type of scenario is very typical. Lots of Meetings / discussions, standups and talking uselessly without jumping in face to face with the actual problem. Things get in the way of the science and facts. Which is why it's important to remove fear, think from first principles and break things down and get your hands dirty.
zacksiri··on Choose Postgres queue technology
There was a fear that having to create an index on a table that large would take a long time, and I think some of it was also ego "I intentionally didn't add it in, because so and so reason". This was why I dug in and did my thing, debunk all the fear / opinions / rationalization. Sometimes you just gotta be able to tell people they're wrong supported with empirical evidence. That's how the team will grow. There is just no need to dance around facts. I remember having to tell the team, "taking a long time to run an index is no reason to avoid creating the index".
zacksiri··on Choose Postgres queue technology
During my tenure as CTO at a fintech company I built a banking engine using postgres backed queue system using Elixir / Phoenix. It's still in use today. The company processed large volumes of transactions and we were able to do things in real-time in terms of payments. Our system reached a point where I realized that we can scale almost infinitely just using a 2 tier architecture (Elixir / Phoenix / Oban and PostgreSQL)

The industry standard for real-time was anything under 30s end-to-end. We hit many scaling limits as our platform grew. We worked on improving the system instead of looking at postgresql as a problem. We measured and measured and postgresql was never the problem when it came to scaling. Most of the problems that existed was mostly due to design decisions in the system or some technical debt that needed to be solved. When we solved those problems the system flew.

There was one incident where our PostgreSQL instance CPU usage went up to 100% during peak hours and would cause problems in the system. We wondered why, there was a lot of debate around the topic, PostgreSQL doesn't scale, we need a larger instance, or move to a dedicated queue system etc...

I didn't believe the hypothesis that PostgreSQL didn't scale. So I conducted a performance audit on the system myself I discovered one of the engineers forgot to add an index on one of the columns on a major table with > 60m records. There was a lot of back and forth between engineers that discussed whether we should add the index. I simply conducted a small experiment and PG analyze clearly showed a missing index in one of the key tables. After we added a single line of code and deployed the index, during peak hours DB CPU usage would not even exceed 20% we had to scale down our DB to save some $$.

PostgreSQL backed queue system does work.

I've been building distributed systems in large and small scales for over a decade. Before building systems with Elixir / Phoenix I also used to work with Rails where the default is as mentioned in this article is you just adopt Redis. While Redis does have additional overhead when it comes to management of the infrastructure, it also worked well.

Having been through both I'd say a simple PostgreSQL backed solution is the clear winner when it came to not having to manage a 3rd dependency when you already have a complex system. There was no 3rd or 4th piece of the puzzle to theorize hypothesize or experiment with. You just had 2 pieces it is either your application or your database that's the problem. That simplicity saved us a lot of time for debate and doing experiments also squashed any dogmatic values and opinions that just didn't hold any water.

zacksiri··on Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps
Do you have any plans on releasing an Ecto Client? Basically What I would like to do is deploy my phoenix app at the edge, and have a postgresql database centralized in some other region. Let's say for example my centralized postgresql is in us-west-2 and the client running in ap-southeast-1.

Would something like this be possible?

zacksiri··on The past is not true
Yes I did assume the "news" being local news media covering the case. I guess this is a prime example of what could have also happened. Sweet irony.
zacksiri··on The past is not true
It's not that the past is not true. The past is true, what was reported is not. We know very clearly where the problem lies. The media is a lie. Headlines like "she'll never walk again" sells more than "she'll be fine".
zacksiri··on LXD is now under Canonical
Very soon. I would say in the next 2 months.
zacksiri··on LXD is now under Canonical
If you use LXD you don't need Podman, the main difference between LXD and Podman is LXD runs System Containers while Podman runs Application containers.

One advantage of having a system container is you can use a package manager to update your applications. With Podman, you have to replace the entire container, with LXD you can just "PATCH" the container. This results in much faster upgrade / lifecycle management.

You can read about this on my blog post. https://zacksiri.dev/posts/why-i-created-pakman

zacksiri··on LXD is now under Canonical
I've been a long time user of LXD, it's an amazing project. It basically served as an alternative to kubernetes / docker for me. Enabled me to launch projects and build companies without being bogged down by the complexity of kubernetes.

I've created a project called instellar https://instellar.app which uses LXD under the hood. I'm working towards open sourcing instellar. It basically automates continuous deployment pipeline and automatically manages your infrastructure. Basically you get a heroku in a box.

I see a lot of people complaining about snap here. In the initial days yes, snap's auto upgrade would bring down a cluster, however I believe they've resolved this issue. Currently from my experience things are really smooth between upgrades. Basically invisible to me.

Hope this change brings LXD forward, and while the team may "regret the decision" I do hope they continue to work on LXD.

zacksiri··on Show HN: Run your own Vercel in minutes
Creator here. We are working towards open sourcing the platform. We’re looking for feedback. Give it a try and let us know how it goes!
zacksiri··on Work Distribution with Jump Consistent Hashing
That looks cool! Seems like I have a new toy to explore!
zacksiri··on Ask HN: Most interesting tech you built for just yourself?
Nice! Good to see others are tackling the same problem!
zacksiri··on Ask HN: Most interesting tech you built for just yourself?
I've been working on https://instellar.app. It's a SaaS product that will enable anyone to turn their own infrastructure into a PaaS without needing to hire a DevOps.

I did this because I've had problems hiring DevOps (lack of resource / lack of people to hire / and kubernetes was just too complex). I decided that I need a tool let's me have my own heroku on my own infra and here we are.

zacksiri··on iOS 17 app sideloading might only be available in Europe
You can do some further reading here

- https://www.bangkokpost.com/business/2524469/mobile-banking-...

- https://www.nationthailand.com/thailand/general/40024972

Enjoy!

zacksiri··on iOS 17 app sideloading might only be available in Europe
I'm simply presenting a case in my own country. Where I've seen the negative effects of sideloading playing out. People's livelihoods are being destroyed.

I do understand that sideloading is something desirable for some percentage of people.

Point is every thing has pros / cons. Sideloading is like buying a car and upgrading it with NOS. Yeah it's wonderful. Your going to have a very powerful car. But the risks also increase. Most people don't need NOS in their car.

I'm speaking for most people. In my household I recommend everyone to use Apple devices, it keeps them safe and happy.

Ultimately everyone is entitled to their own choices and have to accept the consequences. I guess we'll have to wait and see how it plays out now that it's coming to iOS 17 in the EU.

zacksiri··on iOS 17 app sideloading might only be available in Europe
Right, but for Apple to take down those apps, it's much easier than taking down some random link the fraudsters put up.

I'm not saying iOS is 100% bullet proof. I'm saying the problem is much more manageable without sideloading.

← PreviousPage 3 of 4Next →