There is one that I have learned in the past few months and that I am bad front end designing, but I have been wanted to make a portfolio page for a while. I haven't quite grasp the concept of github pages and will hopefully figure it out soon.
In the meantime I created a Webydo page and linked it to brianllamar.com
After next week I hope to start learning Javascript, and other things besides bootstrap.
Showing posts with label porfolio. Show all posts
Showing posts with label porfolio. Show all posts
Thursday, February 27, 2014
Friday, January 24, 2014
Task Off - App #3
The heroku page for Task Off is Taskoff.herokuapp.com - Please try it out. The concept did come from Bloc and not something I will be purusuing further, So feel free to fork it and have fun.
The code is on my Github and here is the Gist I started this from. I will be starting Block Marks tomorrow morning and excited to implement different concepts.
The code is on my Github and here is the Gist I started this from. I will be starting Block Marks tomorrow morning and excited to implement different concepts.
3rd App complete: Checking logs for errors.
I am just about to finish my 3rd month learning programming and stoked that I have completed my 3rd web app. I spent about 20 hours building it and maybe another 5 this week cleaning it up. This was also my first app that I did not follow a tutorial to build, although I did reference some old tutorials for specific things and used a Rspec tutorial as a guideline.
I am looking forward to starting my 4th app Blockmarks, which involve quite a few things I have not implemented. More on that to come.
I do want to pass on some advice as well as remind myself to check the logs when debugging. I always start with the error on the localhost page but alway forget to check the "rails server" log for the root of the issue. I found a pattern when I kept getting stumped and going to my mentor for help, only to find out my answer was in the log.
This morning I had an error running my app on the Heroku. I wrote a long message with embedded code to my mentor and realized I did not even check the heroku log. I ended up deleting my message and will work on the solution some time today. I will share the app later once I get a chance to fix. For here is the Github
Remember to check your logs. cmd+f "error"
I am looking forward to starting my 4th app Blockmarks, which involve quite a few things I have not implemented. More on that to come.
I do want to pass on some advice as well as remind myself to check the logs when debugging. I always start with the error on the localhost page but alway forget to check the "rails server" log for the root of the issue. I found a pattern when I kept getting stumped and going to my mentor for help, only to find out my answer was in the log.
This morning I had an error running my app on the Heroku. I wrote a long message with embedded code to my mentor and realized I did not even check the heroku log. I ended up deleting my message and will work on the solution some time today. I will share the app later once I get a chance to fix. For here is the Github
Remember to check your logs. cmd+f "error"
Subscribe to:
Posts (Atom)