mateusfreira
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.
Why (Neo)Vim is not for you
Code Coverage for Rust Projects with GitHub Actions
NunDb is now referenced in the Database of Databases
Reviewing Changes [open source crash course] [video]
HashiCorp strikes OpenTofuOrg back and more [audio]
Open source small business in real life Oban [audio]
Node.js: The Documentary [video]
I am a little skeptical with documentation fully written by AI will not became too verbose
Consulting to Fix AI-Created Software May Be Our Next Big Opportunity
The work on the type System seems to be going well and the work on machine learn is starting to get attention
"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.
Secrets for becoming a better developer in 2024
Keep up the good work, folks
How to Chaos Testing with Docker and Toxiproxy
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.
I run my business for over 10 years and have experimented many different alternatives, for small business with no cash to burn this is probably the best advice one could gave.
Start with consultancy/freelancing reduces a lot the risks
Show HN: POC: Real-Time Medical Image Collaboration Made Easy with OHIF / Nun-Db
* $ 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?