Skills
An In Depth Discussion on My Skillset
A Little Background
How I Ended Up Here
I've always been a musician. I've been playing piano for 18 years and have been a piano teacher for six, so I've always had an outlet for my creativity. In college, I pursued Electrical Engineering, since I was pretty good at math and I believed I could bring some of my talents and creative thoughts here. Though school taught me to be creative a be a critical thinker, it didn't necessarily give me the tools and skillset to really pursue what I wanted to make. After graduating, I ended up coming to Flatiron School, learning how to be a full-stack engineer with an emphasis on Ruby on Rails and React. Now, I'm looking to bring my musical apitutude, design ability, and coding skills to create innovative apps with real life purposes.
Quote
Any fool can write code that a computer can understand. Good programmers write code that humans can understand.
-Martin Fowler
let i = 0;
let array = [];
isPresented = () => {
if (!array.includes('Ruby' && 'React' && 'SQL' && 'HTML & CSS' && 'JavaScript')) {
return true
} else {
return false
}
}
while (!experience.isPresented()) {
print 'Iteration ' + i;
i++;
}
print 'It will take ' + i + ' iterations to go through my experience.';
Timetable
Time Spent On Each Subject
| Subject | Timestamp | Length |
|---|---|---|
| Ruby On Rails | March 2019 - October 2019 | <1 year |
| React | March 2019 - October 2019 | <1 year |
| SQL | February 2018 - October 2019 | 2 years |
| HTML & CSS | January 2015 - October 2019 | 4 years |
| JavaScript | February 2018 - October 2019 | 2 years |
In Closing
Many people see programmers as robotic, sentient creatures who only work towards one goal in mind and without much thought to others. A lot of the time I spent working on these projects made me realize just how much creative potential to programming. Whether it be a simple SQL table relationship or a small CSS change, there are always design choices happening when one is writing code. Even the code itself can be flexible - one person might have a different approach to the same problem through a recursive solution with a different runtime. Ruby on Rails has taught me how to be a backend programmer capable of making migration tables and writing CRUD methods. React showed me that there are always going to be evolving methods of older languages through creating distinct components. SQL made it possible for me to understand what exactly my backend was doing when it was inserting thousands of rows of data into my table. HTML & CSS were my gateway to making my applications look presentable. And finally, Javascript showed me just how difficult navigating a single-threaded language can be with asynchronous callbacks, as well as how to traverse a tree and a DOM.
I now think the most difficult part of programming is not the recursion, nor knowing the multiple types of data structures, or even learning every single possible language. I personally believe writing code that anyone can understand, especially nonprogrammers, is the hardest part. The best programmer can write code that can quite possibly be the most efficient thing ever, but it would probably be hard for others to collaborate with him depending on the level of depth that the code is written in. Instead, it should be noted that efficiency should never initially be taken over simplicity. Furthermore, I sometimes think my lack of programming knowledge in some subjects gives me a heads up on others who are well traversed in the subject (not technically of course). I always feel a drive to catch up to others and learn from their work, and I believe this is my strongest quality even over all of my other skills that I've listed here.