Hello world!
so this is my first attempt to write a technical blog as recently I started two very interesting book and someone who I know who definitely has more technical knowledge told me to write about whatever you learn even no one reads it. It makes sense to me as well. Maybe I will be more consistent in my learning and maybe I will trying to understand better because I will have to explain it to the world.
Okay now let me mention few things regarding this series of blogs:
I'm starting two books: "Computer Systems: A Programmer's persective"(A book discuss different aspect of a computer from software to hardware to networking) and "Composing Programs"(focuses on methods for abstraction, programming paradigms, and techniques for managing the complexity of large programs)
I will try to write atleast one blog each week but i cannot promise if it will be consistent.
I might stop reading a book for some time(if i get bored) and start reading some other(and write about it) and comeback to above two again.
Before siging off, here is one interesting thing I learned today in "Computer Systems: A Programmer's persective" book about improving performance of a system:
Amdahl's law
is a formula used to find the maximum improvement of a system when only a part of it is improved.
The law is expressed as: S = 1 /((1 - P) + P / N)
Where:
S is the speedup of the system.
P is the proportion of the program that can be improved.
N is the number of processors.
If you throw some number to above formula, you would notice that even though we made a substantial improvement to a major part of the system, our net speedup was significantly less than the speedup for the one part.
This is the major insight of Amdahl's law — to significantly speed up the entire system, we must improve the speed of a very large fraction of the overall system.
Okay. That's all for today. Thank you
Top comments (6)
That's awesome you have someone to mentor you as you learn, I had to push myself on my own to start writing blogs. That's always those first steps when you're just starting, it takes little time until it becomes a part of your life (if you do it regularly); something you do because you're used to (maybe you just like it).
The most difficult is to find something to write about :)
true. thanks man. i'm not going to stress too much in finding something so that i can write. i would rather learn/read something and just write about it. so that i don't force it.
It is difficult start something new. When I wrote my first blog post (sometime in Jan 2013), I could not post it on couple of web sites - it was indicated to me that I am not an experienced writer. So, I wrote my post on my website. The post was about the technical aspects of a small quiz application I had written (and had published it online on my own website). This and couple of articles later I had chance to post my articles on other sites (I guess the experience counted, somehow). My first article was: Java Web Start used to Deploy a Java Application
Cheers on your first technical blog post👍
I have been writing some of these for over ten years now, consciously. Inherently, software engineering requires technical writing - requirements, design, programming, documentation, etc. So, you cannot escape this writing thing.
This is about writing technical articles. Grammar, formatting and decent language are important. It is also a skill. In general, writing your own experience makes a good post. That is my experience.
you are awesome. Thank you for having my back.
Thats great! I'm just starting to do the same thing on my blog. Good luck. <3