I lived in the NL and Brazil, so I can compare the two, and while iDEAL is pretty good, PIX is easier to understand, explain, and deal with.

PIX has more variants, you can use it for recurrent payment, split payments, financing, cashout and almost all things a CC can do nowadays.

I would say Tikkie is almost as good and easy to use as PIX usecase wise but has less adoption and variants, also it belongs to ABN which is completely different from PIX approach.

Comments URL: https://news.ycombinator.com/item?id=48182089

Points: 4

# Comments: 0

I love it but can't understand their differences without leaving the site and comming back for each.

This is a major pain atm with any IDE, they all fight over the same git cmd instance and make a mess out of it. I have a custom setup for this but would like some more integrated way of solving this.

It was amazing to see him decode VISA and MASTER transactions on the fly in logs and other places.

It's written, Florianopolis.

Good luck on the position.

Comments URL: https://news.ycombinator.com/item?id=33799164

Points: 2

# Comments: 1

All the rest was on us, failures, breakages, crashes (We never had one!!!), blocks were super interesting btw!.

So I got on it by chance, I just did interviews as a sport when I was in my early 30's so at some point I passed on this position, pay was awesome, lot's of travel involved, etc... So I joined and learned it all there, it was a small mom and genious software house that specialized on all types of JIT planning for railroads.

JIT was actually "THE" solution to it, because the controllers could just try it during the day, so let's say they new 18:00 was the worst and there was a huge trains comming in at that time with priority, he would just throw shit at the system to see how to same the most time sometimes, of course he knew how to do it by heart, but was it the "Best way" we could help him answering it super fast.

P.S: I am not ducth but I lived there for a while, I remember thinking about how much of a bad day it would have been if it was me, I knew exactly what the NS people were felling :D

Lot's of money to be made on it too if you guys are interested, but it's super niche and hard to get into. There is a huge resistence from train controllers and other workers. I actually understand it because of the job loss involved but it was super cool being in a NASA like control center sorrounded by panels and monitors and seeing the trains moving based on code I and other wrote!

It was a just in time local optimization with lots of heuristics and business rules embedded into it. Basically impossible to reuse between companies or even railroads sometimes, the controller would then solve all the more complex crossing that involved either some lose-lose choice or a pre-defined business decision.

The train controllers are amazing at their jobs, it's super stressful and a single mistake can kill people or make the whole thing stop for weeks, with the software running it made it a lot less risky, one dude could control an area that needed 7 or more people without it, with minor interventions.

I saw it happen numerous times while living there it has indeed hilarious specially because I did it too :D

The most expensive thought of my life was "those fuckers will not tell me what to do".

I don't regret it, since it led me to the best part of my life after that site was eventually shut down 3 years later, but man... Sometimes late at night, alone over a drink, it comes back and bites.

Loved both, both were stolen unfortunately otherwise I would have them.

Comments URL: https://news.ycombinator.com/item?id=30146811

Points: 2

# Comments: 0

The sofware focus on automating tasks other systems don't, document decisions and an extremelly tight link between the budget and the real and projected expenses.

Construction is a very local dependent business so good systems from other countries didn't adapt really well here. Hence the effort to make our own. I am the solo dev.

Stack is

* Backend: Quarkus.io , Lombok and Java

* Frontend: React, Ant Design and Typescript

* Persistentency: Postgres

* Automatic Backup: S3 and custom Postgres container

* Platform: Civo and K3s for PROO

* Security: Keycloak

* CI/CD: Github actions and Cloudflare pages

* Local Env: Docker for local.

* Ide:IntelliJ

Why did I Chose it: * Java and Quarkus: because I have 20 years of experience with Java, it's rock solid, performance is great and I am fast with it.

* Civo and K3s: Because I love k8s but it's too expensive to run for my operation.

* Postgres: It's just great.

* React and Ant Design: I like React approach, I have used Angular and Backbone before and react is awy better. Ant Design is just awesome, great looking components and they work 99% of the time, documentation is also very good.

* Keycloack: because makes me faster, implementing security by your self is always a bad idea unless you are a pro, which I am not. Keycloak let's me focus on the business.

* Github actions: Simple, powerful, free!

* Cloudflare pages: Simple, powerful, free!

Do you think your choices had any impact on your success?

Not there yet, let's talk in 3 years. But we are using the system at my company already and locally it's been a great sucess, improved our work by a mile, people are happy using it even with some bugs, we are already saving money and identifying places where we didn't have a good budget to improve next time. We also are not afraid of people leaving anymore, since with the system their replacements can pickup where they left and continue to work on Day 1 and buy stuff maintaining the time requirements, that was the best part.