HN user

vmsp

600 karma

Software engineer. Built healthcare and recruitment software. Interested in finance, economics and policy.

https://0x1.pt

vmsousapereira@gmail.com

Posts13
Comments116
View on HN
  Location: Portugal
  Remote: Yes
  Willing to relocate: No
  Technologies: Rails, Django, Postgres, React, Node, Next.js, Go, Postgres, Redis, KDB+
  Résumé/CV: https://0x1.pt/Vitor_Sousa_Pereira_CV.pdf
  Email: vmsousapereira@gmail.com
I was founding and lead engineer at a London-based startup that got sold last year. Since then, I've been enjoying a career break, trading some options and working on some projects.
  Location: Portugal
  Remote: Yes
  Willing to relocate: No
  Technologies: Rails, Django, Postgres, React, Node, Next.js, Go, Postgres, Redis, KDB+
  Résumé/CV: https://0x1.pt/Vitor_Sousa_Pereira_CV.pdf
  Email: vmsousapereira@gmail.com
I was founding and lead engineer at a London-based startup that got sold last year. Since then, I've been enjoying a career break, trading some options and working on some projects.

I didn't know I was part of a trend, that's pretty cool. I've been buying originals related to the Portuguese Estado Novo and Carnation Revolution for some years. A ton of ad-hoc, clearly political, publishers spawned right after the revolution and I've been thinking of digitizing some of the stuff I have for historical purposes.

Deno 2.8 2 months ago

That wasn't a value judgment on the acquisition. I was just pointing out that it made the project more sustainable.

Deno 2.8 2 months ago

I wonder how Deno's faring.

Node's the stable solution and will be with us forever. You can now use TypeScript with it and, soon enough, you'll be able to build your app to a single executable -- including native deps.

Bun's chaotic but, nonetheless, it's _fast_ and it's taking an interesting approach by including everything in the stdlib. Plus, bought by Anthropic.

Deno had an awesome story with the sandbox and ease of import for third-party dependencies. Sandboxes feel pretty commoditized now and I'm not sure the import mechanism ended up being that much nicer than a `npm add`.

Everyone prefers real problems. It's something you already know how to do instead of something you explicitly have to train for.

It doesn't change the fact that the real work could be an hour's exercise or longer remunerated work. This isn't an either/or scenario like you put it. Plus, for a fact, companies will happily have you doing both the leetcode and the take-home test.

How does one learn about designing chips, ISAs and the manufacturing process? I feel like it’s hard info to got or, at least, to know how to get started.

Terrific initiative, either way. Open-source chips must be the way.

As a Portuguese I have a more nuanced view of these type of takes.

We invested _heavily_ and prematurely in renewable energies -- see my comment from a couple of years ago [0]. Since then, our energy prices were high for a while and now they're not much lower than the EU's average because all that investment needs to be amortized [1]. Two years ago, we ran a whole month on renewables [2]. Despite this, our increase in energy prices since the Iran war started has been dramatic and the price of everything has been going up significantly. I can't help but think about the ROI on all those renewables if they can't help make our lives easier at a time like this. I'd much rather we go nuclear.

[0] https://news.ycombinator.com/item?id=37719568

[1] https://eco.sapo.pt/2026/03/11/precos-da-eletricidade-e-gas-...

[2] https://www.portugalglobal.pt/en/news/2024/april/renewable-e...

That's perfectly reasonable but, at that point, the argument becomes: build 95% natively and maybe there's a 5% "core" that warrants extracting into a common lib. Technically? That's excellent architecture. In terms of saving development time — which is where stuff like React Native comes in? Not so much.

I hear this and it makes sense but when I actually go about implementing it, it quickly falls apart.

Most apps are UI, remote requests and maybe some storage. What do you put in the common core? Android does HTTP requests one way. iOS does them another way. You go for the lowest common denominator an implement a third way, using libcurl or something?

Or do you just put business logic in the common core? Is there really that much business logic that doesn't issue requests or access a database?