codergv / boot Goto Github PK

I would suggest that in the future, more of our lectures be given in the same format as today. I found that being able to break down the problem as a class or even asking questions to the class gets the students more involved. Out of all the lectures I was able to understand and enjoy this one the most.

@ibolmo

A section on programming a Facebook, Telegram or Allo bots would be awesome.

@ibolmo I would like to request a change in the breakfast and lunch options. We talked about it as a small group and think that having a weekly schedule would be better for everyone. The idea was to have a list of five places and then assign each one to a day of the week and repeat it for the coming weeks. The issue here would be to find the list that works best for a majority of people and fits within our budget. For this I would suggest to have a vote and decide what people like more.

The demonstrations should be slower. We get lost when you type the commands too fast. It helps if you say what you are doing when you type a command we haven't seen. @ibolmo

To whom it may concern (@ibolmo):

Recent studies backed up by absolutely no research and just my insight, demonstrate that donuts are a great way to improve a programming boot course during the mornings. Researchers also speculate that it might be better to just eat fruit but they usually are inside a laboratory so who cares.

I suggest that we create a google drive folder for all the boot presentation slides.
@ibolmo

/cc @ibolmo
From, Software Carpentry Workshop Operations page

Feedback, or "What Are the Sticky Notes For?"

During demonstrations, learners post a red sticky note on their laptop to indicate that they have a question or need help.

During exercises, learners post a red sticky note at the start of the exercise and switch to a green one when they finish, so the instructor can clearly see when everyone is ready to continue, and helpers can see who needs support.

Just before each break, the instructor will ask learners to write down one good point (something they learned or enjoyed) on their green sticky and one bad one (something that they still don't understand or that is bothering them) on their red sticky. It only takes a couple of minutes for the instructors to sort through these, and it tells them whether they're going too fast or too slow, what they need to review after the break, etc. (If possible, someone will mail the sticky notes to Software Carpentry admin after the workshop so we can look for patterns.)

At the very end of the workshop, the host or lead instructor can ask learners to give one good point or one bad one about the entire workshop. This can be done on the sticky notes, the Etherpad, or through a Google form. (This feedback will also be sent to Software Carpentry admin.)

I understand that I have no actual background in this field and was wondering if there was something else that could break down coding in terms that I can understand better? Also a list of what needs to be downloaded onto the computer so that I am up-to-date on all necessary programs 😄

Divide class into two groups, and each group into "pairs" (may be three in a pair). Assign each pair in a group a different coding exercise, to be completed as quickly as possible, with rough code. After solution committed the code shifts to the other group to review and revise for improvement, committing changes. Have the overall group review the changes in each case and present a summary of why changes were made, such as code clarity, efficiency in speed, efficiency in memory usage, etc.

A little late for this challenge but all good now. Thank you @ibolmo for all of the coding wisdom and knowledge you have shared wth the first ever Cod RGV Boot Camp class.

I remember you stating that it normally takes a couple of weeks to build a mobile app and I was wondering what would be the low ball charge to create a simple mobile app from start to finish as a freelance Software Developer? You don't have to be specific but a good $$$ range would be stellar.

Thank you,

Joel Garza

Filling this out to practice at submitting new issues on a github repo :D

@ibolmo

The step by step slide on today's lecture made it a lot easier to understand yesterday's assignment. I think that more of those examples would help us when we're working on own.