nileshprasad137

Work Summary - GSoC'17

The primary aim of my GSoC project was to recreate all the features which were using Smarty Template Engine and remove SMARTY as a resource. It involved removing and replacing UI components that use it, while managing the separation of controller classes and templates, maintaining the object oriented approach. Secondary aim of the project was to enhance User Interface throughout the application and to introduce client side validation.

Smarty Template Engine Replacement

To achieve my primary goal, I had to think of a proper approach to replace the use of SMARTY. I decided to modify the existing controller classes to work independent of Smarty class, by replacing Smarty defined functions like fetch(), display() and assign() using the concepts of output buffering in PHP. I made 3 pull requests to completely replace Smarty from LibreEHR.

Here are the Pull requests to achieve my primary goal :

1. Removed the Smarty dependence of Controller Classes and completely revamp Admini

nileshprasad137

LibreHealth

Issues Reported

Complete List

Pull Requests

Complete List

---

nileshprasad137

curl --location --request POST 'https://YOUR_AUTH0_DOMAIN/oauth/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'client_id=YOUR_AUTH0_CLIENT_ID' \
--data-urlencode 'username=YOUR_USERNAME' \
--data-urlencode 'password=YOUR_PASSWORD' \
--data-urlencode 'grant_type=password' \
--data-urlencode 'scope=openid'

nileshprasad137

FWIW: I'm not the author of the content presented here (which is an outline from Edmond Lau's book). I've just copy-pasted it from somewhere over the Internet, but I cannot remember what exactly the original source is. I was also not able to find the author's name, so I cannot give him/her the proper credits.

---

Effective Engineer - Notes

• By Edmond Lau
• Highly Recommended 👍
• http://www.theeffectiveengineer.com/

What's an Effective Engineer?

nileshprasad137

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

nileshprasad137

Latency Comparison Numbers (~2012)
----------------------------------
L1 cache reference                           0.5 ns
Branch mispredict                            5   ns
L2 cache reference                           7   ns                      14x L1 cache
Mutex lock/unlock                           25   ns
Main memory reference                      100   ns                      20x L2 cache, 200x L1 cache
Compress 1K bytes with Zippy             3,000   ns        3 us
Send 1K bytes over 1 Gbps network       10,000   ns       10 us
Read 4K randomly from SSD*             150,000   ns      150 us          ~1GB/sec SSD

nileshprasad137