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.
HN user
basdp
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.
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...
[1] https://www.raspberrypi.org/documentation/configuration/wire...
Uh yeah.. cool? What makes it relevant for HN?
But most of these are 16-bit...
They do, but psychologically they design the shops so that you get lost and see a lot of 'impulse-buy' sensitive items before you even get to the place you want to be.
How many years did SpaceX do over that modern rocket? How many years did NASA do to get to said modern rocket? I'd say he's on a pretty good roll.
From your timesheet I see that there are more people taking more than 20 days off, than not. This seems to contradict your premise..?
Except busybox allows execution of external binaries. And BB is much (MUCH) more complete. Let that sink in.
This is just a very simple frontend to this library: https://github.com/holzschu/ios_system
That library is just a simple implementation of some basic commands. It does not do any executable execution, it does not use the real system utilities. Nor does it has anything to do with Bash, or shell scripts. It’s just basically one big ‘switch’ for all commands, which are implemented in the app itself.
What is a pipeline problem? Never heard of it before.
Try to port it to Android next, great fun! You’ll appreciate iOS more after that ;-)
Are you using non-apple servers or other devices in your home network? If not, that’s probably the reason of most net related bugs. Also, do not try to do things manually on Apple machines. Do not “copy files” if you want to sync photos, instead, do it the Apple way. It sucks, but it’s the only way.
Why? Why not just tell the user what is actually wrong?
No. There are a lot of lines of code that are not inside a single printf statement. This is nothing special, just an unreadable clutter of random code.
Perhaps you should start by sharing yours!
What the actual fuck... You can automate or collect data about anything, but some things are going just too far. From experience I know that the forecasting and predictions you can do with this kind of data is very, very limited. The time and costs you need go through are way too high. I sincerely question why anyone would use this, aside from the hobbying and gadget-ness of this.
This has nothing to do with building terminal code. This is just a Qt tutorial that has just 1 widget and does nothing special besides the general init stuff for the widget.
This is such a bad idea. 99 out of a 100 times the use case for such a service is because the developer wants to make sure it can spam a real email address.