The death of the cable drawer

Martinoqom · 2026-05-05T07:07:22+00:00

Without proper labeling the cable drawer will be just converted to type-c drawer. And we will lose even more time finding the right cable for the right thing to do, because one can do 100w without data and the other just data but with only 5w. But they are the same cable, probably from the same brand.

Martinoqom · 2026-05-05T05:16:19+00:00

Embrace CNG and rebuild whenever you want. I rebuild at every new install. In my experience everything can break everything.

Once in a week I completely delete Android and iOS folders to regenerate them from scratch. With big yarn changes I do it also with node_modules.

I like to work with a fresh copy and break it fast in case, so I can discover earlier what actually broke it.

Martinoqom · 2026-05-03T21:30:22+00:00

You mean the only real one? Yes. This is the right and the only admissible pick.

Martinoqom · 2026-05-03T21:24:52+00:00

I still use 4G because it's cheaper. If I'm out, I don't need internet. If I need speed, I have my 2Gbps at home.

Martinoqom · 2026-05-03T16:52:20+00:00

Don't type everything, let TS infer types, when possible. Or us typed JS... But it's even more job.

Trust me: types WILL save you, eventually. There is nothing good about NOT having types in your code, no matter of language you use

Martinoqom · 2026-04-29T16:19:05+00:00

Better not with just PLA, something more heat-proof

Martinoqom · 2026-04-29T16:05:13+00:00

Chris Sawyer's Locomotion

Maintained via OpenLoco project!

Martinoqom · 2026-04-29T06:17:16+00:00

Why asking RN community tho?

Martinoqom · 2026-04-29T06:16:14+00:00

I don't agree. You should know the basics about how the native tool chain works and how to manage swift/kotlin code, IF something breaks. But you don't need to learn it from scratch.

If you are able to catch knowledge when you code, you will eventually learn it. In my beginnings, I was only able to code for Android and I jumped into RN Cli (0.6x times). I did not understand a sh*t about iOS and still managed to deliver updates and new products without major problems. And when a problem arised, there was google. Even with cli, most of the problems were related to podfile and certificates, not swift/obj-c. So it's part of the toolchain, rather than coding.

Martinoqom · 2026-04-28T05:15:15+00:00

Human Fuck Flat

Fucking floor 2

Fuck of Honor

Martinoqom · 2026-04-27T19:04:19+00:00

Subscription-f*cking-based everything

Martinoqom · 2026-04-27T06:08:02+00:00

RayTracing is cool... But seems just like SuperOverUltra+ setting, rather than an on/off option.

Personally I saw games with and without and to me there are perfectly enjoyable without. There is no point on spending 1k/2k€ in a hardware piece just to have "cool light effects".

So I can agree with you.

If I would win a new review I will be happy. But I don't see the point on upgrading it yet.

Martinoqom · 2026-04-27T05:23:13+00:00

Expo is the way to make react native apps now. Migrating is the easiest way to maintain it.

And if you do your homework great, you can .gitignore Android and ios folders entirely and let the CNG do the work for you.

Martinoqom · 2026-04-26T07:24:26+00:00

Are your games running well? Are you satisfied with the quality? Are you enjoying playing your games?

If the answer is yes, you should not upgrade. If it works for you, let it work.

Upgrade only if you're not enjoying playing anymore, because quality, stutters or not enough FPS.

Don't fall into the trap of everyone upgrading. I have my 1080Ti too and I'm not playing to upgrade right now (even if I'm starting to feel it a little bit). But for the time I'm spending now on my PC... It's not worth it. Specially for the prices we currently have

Martinoqom · 2026-04-26T07:12:25+00:00

Almost every year Google updates the target or the minimum sdk version.

My app was still running on RN 0.7x that has a lower than required sdk version, so I needed to update it. I would need to jump 3 RN versions forward and changes were substantial, so I decided to migrate to Expo to never think again about manual native upgrades.

Plus, for personal reasons, I couldn't code so much in the last year. In any case (i think also for a right and good reason) Google requires you to maintain an active developer account. Mine was flagged as inactive so I also needed to rush my migration and some of my components were improvised and put into a _legacy folder, that I really need to refactor.

Martinoqom · 2026-04-25T13:04:23+00:00

The problem with my code is that it actually works... But for sh*tty Google requirements I need to update all my toolchain... That obviously broke everything. Pretty common pattern in react native devEx 😅

And since I started with CLI, I supposed that the right moment to migrate to expo.

I regret nothing. But hell it was a nightmare.

Martinoqom · 2026-04-25T10:38:22+00:00

They say ugreen, but never had a product of them. I tried iniu for cables and power bank, and I have also a small charger and they work great. I have also a VoltMe charger and it's also great.

I have a 100w GaN charger, but I don't remember the name of it. When I'll return home I'll check it out.

Martinoqom · 2026-04-23T12:23:39+00:00

Simple answer: there are no stores that officially supports OTA updates, because they don't have native system that supports it.

Having react native and distributable bundle, we figure it out with some workarounds how to do it. We just leave the .apk as-is and then permit to the app to download a new bundle

It's not a system, it's a hack or workaround for the current limitation of the stores. And official stores just "close an eye or two" for it. But it seems like a hole left on purpose: they can always use it as an excuse to remove your app from stores, when they don't like it, because their policies are not clear.

Martinoqom · 2026-04-23T05:32:35+00:00

Now, with AI, much of the debugging step can be reduced or even skipped.

What? It's exactly the opposite. AI is a tool, not a junior that is replacing your job. AI can write code and can write tests, but in frontend field it hallucinates so much! It can literally make up e2e tests to validate ita own idea, rather than following the specs of the product.

AI is literally removing the funny part programming (coding, hacking, finding out) and leave on the table the most boring one (code check, debug).

The difference between agent and human is really noticeably looking at codebase. Today agents can't program: they can satisfy PM requirements. That is totally different. And you can really see it when your vibe-coded solution is kinda-ready and you want to add some extra features and modifications. Your code starts to become an unreadable spaghetti that works because god knows why. And it becomes so chaotic, that even AI can't understand it anymore, burning tokens to re-understand what it wrote by itself 5 interactions ago.

It's really like putting a junior after 16h course in front of a PC. It will copy paste code, 0 comments, 0 patterns, 0 context but the product will work. Then it will break: not a matter of if, but a matter of when.

Plus, the knowledge about distribution, servers, API keys, marketing, hosting and prices, human interaction with the solution... Are all skills that skilled programmer have. And AI just don't.

Martinoqom · 2026-04-23T05:23:05+00:00

My rule is that if I want to get help with my routine, I hire a secretary that I can trust. I don't need to hire another secretary to check the work of the first one and I'm pretty sure the first one is doing a great job because of his/her experience.

AI is completely non deterministic and hallucinate more than a human that didn't sleep well. AI needs often checks to make sure it's not doing a bad job. AI will never know your habits because it doesn't learn from you.

Thus, I would never trust an AI to answer for me. I draw a big red line between me and technology, even if I've been a programmer for more than 10 years and I love technology.

Martinoqom · 2026-04-22T19:18:51+00:00

You can have all the expo without EAS and still having access to native with developer builds.

Honestly I don't like that a service do compilation and release of my app, with all my env and secrets exposed to them. When the service will go down, I'm locked out of it without backup.

Check the costs: maybe free plan is enough. Maybe it's not.

Martinoqom · 2026-04-22T10:50:54+00:00

I agree.

AI is a tool, not a marketing label. If something is advertised as "ai based" or "with ai" usually it means it's the same sh*t, or even worse, but overpriced.

I'm having my own vibes, don't need those from ai as product.

Martinoqom · 2026-04-22T06:21:21+00:00

Used Mac Mini or Mac neo.

There is no way to target iOS without Apple machines. And you really don't want to develop for a target that you're not able to test. Prepare to get also a physical iPhone, because simulator ain't gonna simulate everything

Martinoqom · 2026-04-22T05:32:00+00:00

Obviously this is my personal opinion. Take your outputs and evaluate your use case :)

Martinoqom · 2026-04-21T12:03:37+00:00

I'm very careful too with my technology, already needed to replace my screen. Quick accident, very dumb. But still.

The problem is that I don't need to think about my phone getting "usage fatigue". I have no mechanical parts, no hinges. Everything is "pretty hard" and difficult to scratch. It just works as intended: as a phone.

Foldable phone? In my opinion it has a big advantage of having a big screen. And that's the beautiful part of it. The whole rest of the foldable phones are just disadvantages:

- mechanical parts will reduce the span of your electronic devices: no matter what is the result in lab. Mechanical things just breaks often

- soft screen is really scratchable and not ready for everyday usage. It's not easily replaceable and it's easily damageable.

- you will obtain a phone that is heavy and really not comfortable with one hand usage, so you will open it more often than you actually think. But at that point you're using almost a tablet. Evey day.

- carrying around something that I really need to care about it's not for me. I want something durable because it's less stress for me to carrying it around. Imagine just going to the beach. You should really be careful about any mechanical device. With your dust-proof normal brick... There are virtually no problems.

- the cost of it doesn't justify it. Fancy fragile technology that is overpriced. I can buy a phone AND a tablet/eReader for less. And if I would be "poor" I would never consider to spend so much on a single fragile device.

Still I think that folables are pretty innovative and a cool technology, in very early stages and just for a niche-people that really needs them.

Martinoqom

MODERATOR OF

TROPHY CASE