I remember I blogged about Laravel back in 2016 (time flies!), and reading them again, I am surprised that what I thought back in 2016 still applies today.

Today I am going to talk about some black magic I’ve encountered writing a test blog project. The bit that filling out the blog form and validating the data. Normally, when a form is posted to an URL, the controller validates the form data and throws validation exceptions if form is not validated, then the controller can redirect the browser back to the form along some error data to be displayed on the form. In Laravel, the redirecting back to the form is automatically done for you and somehow the view magically has the ‘errors’ variable in context.

//www.youtube.com/watch?v=xoLmVFAFjn4

We also know that Yellow NZ has a lot of connections with SMEs. It can utilise this advantage to venture into areas that actually help these SMEs to do their business, such as providing a platform for ecommerce, booking, trading etc etc, which ultimately creates an ecosystem that benefits both sides.

My hypothesis (not being a scientist and without doing any search) is that time is merely a concept of a counter, which is different to the chronological sequence counter “CSC” (I just made this term up) in 4th dimension.

In an analogy, our world is like a running program try its best to keep track of time internally during execution, this is encapsulated and sealed within the 3rd dimension. If this running program cannot conciliate with the system clock (CSC in 4th dimension), that means the running program will eventually out of sync.

I am not aware of any ways to conciliate with the CSC nor how to measure CSC at first instance.

It seems to me “time” does not live in 4th dimension but merely our conception.

The graph below is the connection graph tethered on my phone on 3G Mobile Data, comparing to above, a lot less connection drops.