HN user

mateusfreira

111 karma
Posts30
Comments53
View on HN
carbon-steel.github.io 2y ago

Why (Neo)Vim is not for you

mateusfreira
1pts0
blog.freira.dev 2y ago

Code Coverage for Rust Projects with GitHub Actions

mateusfreira
1pts0
dbdb.io 2y ago

NunDb is now referenced in the Database of Databases

mateusfreira
1pts0
www.youtube.com 2y ago

Reviewing Changes [open source crash course] [video]

mateusfreira
1pts0
twitter.com 2y ago

HashiCorp strikes OpenTofuOrg back and more [audio]

mateusfreira
1pts0
changelog.com 2y ago

Open source small business in real life Oban [audio]

mateusfreira
2pts0
www.youtube.com 2y ago

Node.js: The Documentary [video]

mateusfreira
40pts0
mateusfreira.github.io 2y ago

Consulting to Fix AI-Created Software May Be Our Next Big Opportunity

mateusfreira
2pts2
mateusfreira.github.io 2y ago

Secrets for becoming a better developer in 2024

mateusfreira
2pts0
mateusfreira.github.io 2y ago

How to Chaos Testing with Docker and Toxiproxy

mateusfreira
1pts0
mateusfreira.github.io 2y ago

Show HN: POC: Real-Time Medical Image Collaboration Made Easy with OHIF / Nun-Db

mateusfreira
2pts0
mateusfreira.github.io 2y ago

On-Call Shifts Compensation and Scheduling for Small Engineering Teams a Propose

mateusfreira
1pts5
github.blog 3y ago

GitHub: Survey reveals AI’s impact on the developer experience

mateusfreira
1pts0
mateusfreira.github.io 3y ago

Match vs. Hashmap Which one is faster in the Crab Language?

mateusfreira
1pts0
changelog.com 3y ago

[Podcast] How do you do, fellow Hack Clubbers?

mateusfreira
1pts0
mateusfreira.github.io 3y ago

Mob Programming: Pros/Cons of Full Team Collaboration on a Single Screen

mateusfreira
1pts1
mateusfreira.github.io 3y ago

Secrets for becoming a better developer in 2022

mateusfreira
2pts0
mateusfreira.github.io 4y ago

Argo workflow as performance test tool

mateusfreira
2pts0
world.hey.com 4y ago

I ain't no angel but I have made some startup investments

mateusfreira
1pts0
changelog.com 4y ago

Run your home on a Raspberry Pi

mateusfreira
76pts85
book.goose.rs 4y ago

Goose Load Tests in Rust

mateusfreira
2pts0
www.cornerstonejs.org 4y ago

Cornerstone3D Is Out

mateusfreira
2pts2
changelog.com 4y ago

Learning from Incidents [audio]

mateusfreira
2pts1
news.ycombinator.com 4y ago

Meilisearch raises a $5M Seed to change the world of user-facing search

mateusfreira
2pts10
www.youtube.com 4y ago

Kubernetes: The Documentary [Part 1]

mateusfreira
2pts0
changelog.com 5y ago

Podcast changelog scale and ultra-resilience

mateusfreira
1pts0
mateusfreira.github.io 5y ago

A fast to sync/search replication algorithm written in rust

mateusfreira
7pts2
mateusfreira.github.io 5y ago

When pure agile is falling apart, ShapeUp might be the way to go

mateusfreira
1pts1
mateusfreira.github.io 5y ago

Secrets I use to becoming a better remote developer

mateusfreira
20pts5
mateusfreira.github.io 6y ago

Making the react+redux+saga development more fun, productive and less repetitive

mateusfreira
2pts0

Most people don't think about that. Once they realise things change, Brazil also uses Bitcoin a lot because of a lack of trust. Pix would be even more widely used if the government took longer to start using it as a weapon (as it has already done)

Pix has become virtually liquid cash here in Brazil. We use it for everything from tipping a waiter to buying an apartment or house in seconds.

Before the release, when I read about the system, I was skeptical, but after its release (approximately 5 years ago), it has worked seamlessly, and adoption is now nearly 100% across the economy.

Elixir is going in a very interesting direction, it may be the Language to I will learn this Year

The work on the type System seems to be going well and the work on machine learn is starting to get attention

I never correlate my growth with the company I am working for; sometimes, you overgrow the company, and it is time to leave.

"Pays okay; 100% remote; very few meetings; low standards for productivity mean I have great work/life balance" seems like a perfect workplace.

What you need is probably a project outside of work to challenge you. I built my own company 13 years ago as a side project (I still run it up to this day as a side project) because I was a Mobile developer and Would like to keep doing Web development.

Today, I am having fun with my Open-source project https://github.com/mateusfreira/nun-db. When I have too many meetings or fight fewer coding challenges in my work, writing my own distributed database keeps me fresh and challenged. With it, I learned Rust and also distributed systems, which made me read books and papers that would never be needed for my normal work.

I see that as growing, and it has brought me great opportunities. Times these side projects become companies, and you make money; times, they bring job opportunities that you would not have otherwise.

You should leave a company when your growth is faster and more than the company can take in. Meanwhile, use the low pressure to go after other challenges personally; that is my way of dealing with it.

What is your stack? There are areas with more opportunities than others that may be worth considering a stack shift.

I have been in the market since 2006, and I have seen it go up and down; I've never been unemployed since, but I have close friends who run over one year without a job (In Brazil, we usually have financial crises here more often), at that time their option was to do freelancing for a while until they find another job.

I never felt "safe", having entered the market in 2006 and seeing very senior devs losing their jobs in 2008/2010; I founded a company in 2010 and run it up to this day as a side project (A SSAS for small business), of course, it takes time to build one of those (In my case it took over three years to get the first five customers, today we have more than 1k), and it is a counter sense to spend time building a business that will make you 2k UDS when in your work you can earn 5x that working on a company and having vocations. Still, it does pay off in times like this since I am not too worried if the marketing goes terribly; I can make a living with my side project.

TLRD: There is no perfect set for small teams, but here is a try.

* $ Compensation Paying 5% of the hours for the on-call time, being paid or taking time off, with time off that can be accumulated to be used for longer periods. 24 hours * 5% * 7 days = 8.4 hours.

* On-call shifts frequency and time to react requirements With two people, one can be on call every other week and take two days off monthly to compensate. For example, one could take every other Friday or one Friday and one Monday off. 52 weeks / 2 (every other week) = 26 weeks on call an year. Time off is fine for on-call Time but not for time in action; Time during outages is much more stressful than normal working hours. Offering time off in exchange for working in outages is not fair. Therefore, for those cases, I think paying for the normal working hours will be the right thing to do, of course, more time off is fine too. If the team grows to four people, one can be on call once a month and have a day off a month, too. The cost stays the same, but it delivers an easier-to-handle situation for the team

What do you guys think?

I am currently developing an open-source (MIT) database that can be directly accessed from the frontend (browser and apps) , that is distributed, and capable to deliver data in real-time. The primary goal is to provide support for any use-case that requires close proximity to users and, most importantly, it is entirely free to use and run by yourself if desired.

If you would like to view it, please visit: https://github.com/mateusfreira/nun-db

Feedback is always welcome, especially if you have a use-case in mind that you believe it may be suitable for but are unsure. I have already utilized it in many of my personal projects and for a few clients with a small number of users, but I am hopeful that it will soon be ready for larger-scale implementation. Comments here, issues on GH or emails are welcome

TRLD version: Mob programming is a great technique; in all the opportunities I have applied it, it has been very helpful. It can be expensive and you will need to have a strong and mature team to make it work. It works quite well in a remote environment, provided the team is willing to work with it. If you have not yet tried it, get your full team on a call, pick the hardest problem you have to solve, and start coding it and taking decisions just-in-time, and share your experience later; the results will speak for themselves. My only concern is how demanding it can be; if you try to do it for too many hours a day, too many days in a row, be careful not to burn yourself out in the process.

Automerge 2.0 3 years ago

Great improvements, performance was probably the major concern of automerge prev versions, I have begin reading about CRDTs and this is the correct movement field at the moment.

Local first in my mind means your users can still work even if your server is down for a small amount of time for any reason, which means the users can also jump on an airplane and decide to review/update their price table or check out their sales commissions if they want. It benefits both sides of the software economy (users and providers)[1].

I recommend the reading the paper from 2019 about local first it is not too academic and gives a good view of the challenges [2].

[1] https://mateusfreira.github.io/@mateusfreira-2022-12-04-my-t... [2] https://martin.kleppmann.com/papers/local-first.pdf

I could not agree more, blogging is fun to write and read, much less structured authors can go as far as they want to make the posts interactive. I still think blog is one of the best tools to share thoughts, and more important to own your content.

Absolutely it maps one to one with Hemingway, idea. It also works very well for personal projects or projects that you rarely have time to dedicate but want to use any opportunity to make process you can

I don't think this is an "An unexpected benefit", I do it like for a long time conceit, that idea is based on "The Hemingway bridge" idea from the Nobel prize winner of literature in 1954.

I wrote about it a few months ago called it "1. Always go home with a broken build"

To experiment and make mistakes that don’t cost me a lot of money or cause too big a problem, I must have a side project.

I wanted to learn rust deeply, and it would be impossible to do so if I had not started NunDB. On Nundb, I can work 10 hours a week or no hours at all without any problem. If I have one hour to code, that is enough for me to do something on NunDB, it requires much more coding than my other two activities, and I still only have a hand full of people using it and only one single critical application, so there I can experiment, learn, have fun.