rooam-dev

Why !MongoDB?

But if it's a better experience for customers, why not?

I am sure customers care about their products lasting longer.

A more future proof too.

Cool. Like a poor man's vaccine. Nature is amazing.

Interesting indeed, perhaps by reducing the quantity of virus we give more time to our body to prepare for the "invasion"?

Long time "intermittent" FreeBSD user here.

I always liked the naming (e.g. NICs) and location of things in FreeBSD, felt more natural to me. It may not be a (good) technical reason, but it makes live so much easier when you know that if I install something it's in '/usr/local'. That said, not sure if it's fair to compare FreeBSD (1 distro) with Linux (many distros).

Better ZFS support would be a good technical reason to use one system over another, so it makes sense to mention it. I did not get the vibe of ZFS being FreeBSD thing either.

PS: I use both Linux (CentOS) and FreeBSD (home server with ZFS).

My guess is that it's a simpler approach. Maildir stores messages in files, so persistence out of the box.

Meanwhile https://thehackernews.com/2020/01/openbsd-opensmtpd-hacking....

My question is how Chrome knows if it's a big impact or not? I assume it's based on metrics sent to google's servers. Can those be disabled?

Yes, it should not matter 3 or 30, once you start to test the higher level/API then some classes don't need a separate test, because they are tested when being invoked by other tested code.

When I hear "add tests" it's always a red flag to me. Imho tests are not optional, they are implied, they are a tool to build your stuff (like scaffolding). If tests are added at the end, how would one know the code written before that was correct?

The later tests are added, the less of their value is leveraged.

It's just a reality check on how much your current ISP has oversold their capacity (similar to overbooking of airplane tickets).

100% agree. The "hacks" and "get stuff done" approach gains quick and short benefit, which probably fits a freelancer/contractor role. Maintainable and testable code should be implied.

It's not about how fast you get to code to production, it's about how fast code/product can be adapted to new or unexpected requirements.

There is a child/lock mode, need to triple click home button (you may need to enable it), however the problem remains if the app has extra buttons that little ones love pressing.

Thank you. Just installed it. I had the same problem with the Notes app. I ended up creating a separate folder for our son, but this is much simpler.

Software engineering is not civil engineering. Software is "soft", "plastic", you can build and change anywhere.

If one could build bridges that easy, I am sure people will do it.

It sounds like you lack some Computer Science knowledge. Try to find/take some, during which you will know what math areas are important if that's your thing.

It's not the same when you go to a tech university to get a B.S. degree in CS, but it's very doable. Nowadays a lot of video resources are available.

Buckle up and good luck :)

How future proof is it? Even if it's quad core, it's still 1.1GHz I mean, will a browser need multiple cores to scroll smoothly through pages in 2-3 years from now?

No 1 on my list is "how testable is the new technology?".

What would be an acceptable free for you?

How should someone grow a product without a/b testing and/or metrics?

Which OS comes without Python pre-installed? But I agree, the less is installed the better.

I use "golden goose" example.

"No amount of automated checking can lead to improved code quality." - Very untrue. The more automated checks (customized to your needs), the less distraction for devs and more focus on things that matter, e.g. quality.

I assume these tools are configurable, so devs could agree what's the balance. We usually start with defaults (assuming somebody put effort into choosing the defaults) and customize as we go.

Pushing without verify and fix everything at the end is worse than not fixing at all imho. After all fixes you basically have a lightly refactored code that has been less tested.

Where they gone?

I think it's perfect for parameter objects

Too much for small classes/records imho e.g. `new Name("First", "Last")` vs. `new Name(first="First", last="Last")`

Also, IDEs can help with parameter hints when is needed.

"BTW, learning Kubernetes can be done in a few days. " - Learn something in a few days and the ability to run it in production are completely 2 different things. Security, upgrades and troubleshooting cannot be learned in couple of days.