Such was r/place, and such is life. There is never a world where there will be no bots and it'll also be completely free for anyone to use online. I'll try to nerf it, though.
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.
That's not perfect btw, many apps today are using websockets (e.g. https://github.com/daltoniam/Starscream) to connect upstream and they bypass iOS/Android proxy settings entirely with no way for http based mitms to see that traffic.
I've found this developer to be trustworthy, has a good track record with his git app. I'd be surprised if he would make this claim if it were untrue... it could easily be proven wrong by anyone using Charles proxy.
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.
One thing I loved about Amazon was having no architects, visio, powerpoints, UML in any of the teams I worked in.
Each service is designed, documented, implemented, deployed, maintained and advertised to other teams by the same few engineers.
Most documentation and runbooks are just text in wikis. If your service cannot be documented without drawing 10 boxes and 20 arrows you should split it in smaller services.
> "There is no value in an architect who doesn’t code"
This is debatable. The OP almost certainly knows how to code, and I think you can still provide quite a lot of value even if all you do is architecture.
It's much like saying a building's architect is worthless if they're not also doing construction work. I don't buy it.
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.
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.
My initial impression is the same as the parent. Juxtaposing microservices and KISS seems weird as the "architectural complexity" of microservices is several times higher than a monolith. You're not only multiplying the points of failure but also increasing the difficulty of translating the domain into code, especially when it comes to reading and writing from a db in a safe and efficient manner. Someone will need to come up with an answer to handling transactional operations that span multiple services sooner or later (or I guess the team can just accept some small percent of data corruption, which is what I'm guessing most companies that do microservices actually do, willingly or unwillingly). Ironically I think the benefit of an architect is a lot more evident in a microservice architecture than a monolith.
Edit: though maybe my view on what an architect should do is different? I think of a software architect as the person that lays out the skeleton and foundations of a project and has the answers to hard questions. Very likely someone who actively codes or has solved very similar challenges to the ones being solved.
you can just put a wpa_supplicant.conf file on the USB stick partition and it will automatically connect to your wifi[1]. This seems like an overengineered approach that is far more complicated...
Never know when you might need to start an insurrection.
"A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects."
