basdp

it's already littered with bots, so it's not fun for a human to go there.

The amount of people writing books on subjects as a way of learning something new, is too high. I’ve seen so much trash these days. Especially game design or programming books.

It is often best to present a problem or a definition in a simplified way. After grasping the basics, we can extend or go into more depth. Otherwise, students can’t see the forest for the trees. Of course it is still important to state that the definition is presented in a simplified form.

This is not hypothetical, as we’ve lived through this before with Internet Explorer. The web didn’t get better from that. Open source is a big plus now of course, but it’s still backed by corporations that want us for our data to make money. It’s never going to be pretty. We might have to live through another monopoly (or we could call it web-communism?) but I am 100% sure we are going to condemn Chromium some time later and work our way back to a free browser-world. It’s the circle of life.

I would like to see the performance differences between the original and obfuscated. Most of the compiler optimizations are being made impossible by removing static access. Plus, a reverse-obfuscator is trivial for all those static-to-dynamic and base64 encoding.

I need proof first. Seen too many apps call home that say they don’t.

The point is that an architect who doesn't 'code' (read: doesn't know how the practical implementation is done) doesn't know what he is designing. It's too abstract.

A structural architect is called the same, but is not really comparable. Apples and oranges. At the least because the Burj Khalifa is still built under the same physics model as they used 100 years ago.

The problem with this approach is that it might be easier to build a monolith, maintaining it and the ops side of it is far more complex.

All the time.

So you're calling (f.e.) Amazon a shack?

Sometimes the answer to the wrong question helps you further down the wrong path.

That's nice! Agile to the max!

Buildings are still built using stones, wood, cement. That doesn't change much.

In my experience as a DevOps transformation expert, 'Architects' are mostly old devs that have been kicked upstairs. The whole world changes each year to an extreme. You have to get your feet wet.

Man, it seems like you totally lost connection with technology. There is no value in an architect who doesn’t code (none, if you think otherwise you’ve worked too long in enterprises that don’t deliver enough value to stay relevant the coming years). Just use whatever drawing tools you know and draw up your diagrams. Should never take you hours to draw them up. How complex are they? If they take you so long, you probably are documenting way too much or are using way too complex architectures.

I feel the solution to your problem is more in the application than the tools. Try moving towards architectures like micro services. KISS. Then use the time you’re freeing up to keep connected to your developers and write code.