pulsarpietro

Thanks all, this is probably a very good starting point

Can't find that chapter here: https://www.amazon.com/Designing-Web-APIs-Building-Developer...

am I looking at a the right edition ?

Thanks for writing this.

I mean .. use whatever you feel comfortable with, make sure you understand what you're doing, the terminal is the closest interface to the OS.

I personally use it a lot but this arguments have been going on over (and over)+ again. And it won't be the last time :-)

.

Many of us have come across them at uni I guess - but there are so many books around. This one always made me smile a bit :

Introduction to Algorithms : Hardcover 1312 pages

Introduction ? :-)

YAUL ?

Anyway I envy you guys, now things tend to be too high level and you lose that holistic view of the computing machine.

Back than you felt pretty skilled I am sure, now I feel anybody could do my job, often. Unless you are working for the big 4 or similar, many jobs don't give you that excitement.

I must have been a bloody hard and interesting work, back then.

I am a bit puzzled by this:

"Before about the early 90s, we didn’t trust C compilers, so we wrote in assembly."

There a lot of games released during the 80's, were they really all written in assembly ?

https://www.myabandonware.com/browse/year/

I don't have experience in the game industry at all, I must add.

Y.A.U.L.

Fantastic, I wish I were born those times.

We need to be more efficient to beat them, there are not other ways.

I have been a Linux user for more than a decade - recently switched to OpenBSD and I must say I agree.

Linux has become a chaotic place to be, I agree.

Me too. I need safe cyber-space to be in :-)

It makes you think of Henry Ford.

I depend on the JVM in my mind traslates to "my target is the JVM"

You are "dependent" if you want on the RunTime (rt.jar). The way it was explained to me, and the model which I sticking to in my mind is:

Abstract Machine/language + RunTime = Level of the onions of a computer.

Assembly/CPU + libc Bytecode/JVM + rt.jar

The language manipulates the resources provided by the machine (registers, stack-machine etc etc).

My recollections are fading though - but I found this model to be good enough to explain me well how a computer works.

Not sure. I have seen people having two windows: 1. Vim 2. Terminal for compiling

I found it quite handy, then I discovered Emacs :-) We could stay on the subject for years I reckon.

Actually I use it in place of screen. I always thought of it as "a better screen"

Yeah, that is what I was taught as well. From one abstract machine to another.

If we think about it javac would not be a compiler otherwise :-)

Well done!

You will need to know the C language, not C++. As with many things you will follow an example, then another, then after a few you will walk using your own legs.

To build a module you don't need to build the kernel, but you do need the kernel headers, you will understand all this once you get to understand a bit of C language, and a bit of assembly won't hurt. Start with MIPS.

You do need a good grasp on the C language, and a lot of time.

I would propose Linux Kernel Development by Robert Love. It is not for beginners though.

That could help you in applying your new C skills in writing a simple device driver/kernel module you can play with. If are really into low level stuff I would propose an Arduino board whose OS is minimal, the Linux kernel is already very complex.

Get a role in an embedded software company and you may learn it all, but some experience is required.

Due to lack of personal knowledge is not quite clear to me what the problem is with mobile devices. It seems to be the fact that they very often change IP address.

am I right ? Is there any resource you would recommend to make my mind up ?

Yeah, same pattern applies so many times, Slack -> IRC + WEB and many others.

>Now that north-south traffic is dwarfed by east-west >traffic in every system [this means that north is the >client, south is your "DB", and east-west just means >services in your system, and since people nowadays use a >lot more complicated systems, the inter-component = >intra-system communication is huge, compared to the few >MBs sent to the client].)

Never thought about it, in those terms.

Yeah, thanks for clarification. As a technical person I find myself a bit confused as I don't know if I should follow some buzz and try to make money in the short term of go deep and go for the long term. Will it pay off ?

Of course I get more satisfaction in "feeling" a "deep" and "true" technical folk.

> And how bad the demand side is when it comes to picking the experts.

You meant, there is a very strong demand ?

> you're always a the mercy of your tools

More than tools they are products nowadays :-(

You are soo right ! There is a shift going on between "operators" and "engineer", many "software engineering" jobs mainly configure and operate on the top of somebody's else product.

They do write code but the technical job, per-se, is not that skilled.

I am not sure it is such a big deal, the old stuff are good enough for the majority of cases, I reckon. He has probably a good point about performance, but pain versus gain I am not sure it makes a lot of sense, on average.

what is it written in now ?