Hi all, I'm Kyle. I'm one of the developers here at Punchmark. I'll be sharing with you my technical thoughts and tidbits of knoweldge on front-end development. My hope is to educate those who are interested to obtain a better understanding of how a website works, beyond what is seen.
Punchmark has a robust software that is bridging the gap for their customer base to be hands on with managing digital needs. There's a huge barrier to entry to grasp any given programming language. Then, there's engineering something useful with it once you have an understanding. I would compare it to formulating a captivating story told in a foreign language you're learning to speak. You start with single words, fumble through sentences, and eventually, over time with a lot of practice, you're voice is heard. Front-end development is the digitial translation of data and ideas. Let's start with A,B,C...
The digital landscape is similar to a physical one. There is architecture, art and science behind building, and we need materials to build. We refer to our materials as a STACK. Here's a list of resources we build with:
PHP - programming language
MySQL - relational database management system
Amazon CloudFront - content delivery network
These resources go hand in hand with PageBuilder2:
HTML - hypertext markup language
CSS - cascading stylesheet
Bootstrap - CSS framework
There will always be bugs. There's an element of trial and error involved with every task. In the front-end world, the errors are referred to as bugs. It's vital to understand why things work the way they do in order to successfully troubleshoot the issues at hand. This comes with developing a healthy appetite of asking why. Patience is also good practice because there are a lot of moving parts. The desire to learn and understand deters frustrations of demanding expectations. This is what we're after. We genuinly want to help and accomodate all of our clients, but it's how we go about it, working together, that makes a difference.
Methodically thinking through what is will get us to where we want to be. When you're trying to solve any problem, critical thinking is common practice. You run scenarios through your head to eliminate possibilities leading you to the answer. The why answers the what, how, where, and when. After solving every problem, take the child-like approach to relentlessly asking why:
What is happening? But why is it?
How is it working/suppose to work? But why does it?
Where is it located? But why is it?
When does it occur? But why does it?
Ask us too, and we'll ask you. The whole point is we have to work together to figure it out. These are the stepping stones to teach what we're working with so that we can work better together.