    
|
|
|
In the recent competitive renewal submitted in 2012, we proposed a new component to our IMSD program called the Speaker Exchange Program where IMSD graduate programs at other institutions would host IMSD graduate students from UMBC and UMB as presenters of scientific talks. While visiting the host institution, IMSD graduates are to also select 3-4 mentors to meet with during the visit. The goal of this exchange is to expose IMSD Fellows to the exceptional research being conducted in academic labs outside of their own institutions. Institutions with IMSD graduate programs at Brown, Emory, UNC Chapel Hill and Baylor are participants of the Speaker Exchange Program. In the spring 2013, Lola Brown, PhD candidate in the Biochemistry and Molecular Biology program and Nicole Barkley, PhD candidate in the Biological Sciences Program gave talks at Brown University and UNC Chapel Hill respectively. Both Fellows will defend their work and begin postdoctoral positions at Yale University (Lola Brown) and North Carolina Central (Nicole Barkley) this fall. Finally, we plan to invite other IMSD graduate programs to participate in the Speaker Exchange Program. Cedric Uytingco, a PhD candidate in the Graduate Programs in Life Science (GPILS) Neuroscience Program has expressed an interest in visiting Rutgers University this spring.
In May 2012, the IMSD Meyerhoff Student Board, a student advisory board for the graduate IMSD program; organized with the assistance of IMSD staff a grantsmanship workshop that included an interactive workshop where participating IMSD graduates were required to bring with them to the workshop their “pre-written” Specific Aims. During the workshop the IMSD Director, Michael Summers and the former Chair of the Chemistry and Biochemistry Department, Dr. Ralph Pollack (retired) would review and provide feedback to the students. Following the workshop, students who were planning to submit their proposals by the August deadline submitted their proposal to IMSD staff who then distributed the proposals to a pre-selected review panel that included faculty from both campuses - Dr. Michael Summers (IMSD Director), Dr. Antonia Antalis (Director, Molecular Medicine Program UMB), Dr. David Eisenmann (biology professor). In July 2012, the student participants re-convened for the second half of the workshop which was a “Mock Study Section”. The review panel selected one proposal to review before the students and provided constructive feedback to the group.
Three (Atum Buo, Jodian Brown and Brittny Davis) of the four students who submitted proposals were funded and more recently, the fourth student received a good impact score and is pending feedback from a resubmission. The IMSD graduate students are eager to host the second grantsmanship workshop. We plan to have this workshop in November 2013 and again in the spring 2014.
As a novice to programming, one of the most common places I find myself in is one of despair. There are many things you need to know to program effectively and early on, try as hard as you might, it’s inevitable to run into problems; that’s part of the learning process. Programming is entirely problem solving, and the key to this whole game is figuring out how to climb out of the ditch you’re in.
One of the easiest ways you can do that is by asking someone for help. But this can be quite intimidating. Often times you feel like you never get the answer you want, and when someone eventually responds, they are quite rude. The first time I posted a question on StackOverflow, I put in a thank you note because I felt that was common courtesy. Instead of getting a response, my question was edited to take the “Thank you in advance!” out and was told to limit my posts to information only.
The seemingly rude response kept me from asking anymore questions on the forum and from then on, for the near future, I tried my best to figure out things entirely on my own. Only as a last resort did I pose a question to someone else. In retrospect, this was the best thing that could have happened to me. Only then did I really start learning.
As part of my job at Treehouse, we moderate a Forum, helping all our students with any questions they have. Often times however, it’s hard to help a student, not because the question is a difficult one, but because they don’t really know how to phrase their questions in a way that will get them good answers. The second, unfortunate problem, is that when they ask a question, they’re expecting a direct answer.
Teachers don’t have a problem with giving you a direct answer of course, but in asking them to do so, you’re really doing yourself a disservice because you’re not allowing any learning to happen. Your brain can’t make any neural connections or any of that cool science stuff. Solving the problem yourself is when you allow the magic to happen.
As a novice myself, I’ve established a good pattern when digging myself out of problems, and I feel like it’s good advice to pass on. A lot of this stuff has already been written on the web in different places so I’ll try my best to bring it all together. So without further ado, here’s my guide, as a novice programmer, on general ways to get unstuck, and how to let the learning happen.
The obvious answer first.
When you run into a problem, there is a very high chance that someone else has encountered it as well. Unless your problem is really complicated or really unique, someone else has already probably asked it and gotten an answer. Your first objective should be to find that answer.
If the first try doesn’t yield an answer, don’t give up. Maybe your query was too broad, or maybe it was too narrow. Phrase your search query differently and see if that works. Don’t just click the first link expecting results either. Navigate through the search results. Some may be similar to your problem and while not the exact situation, could provide you with the guidance you need to solve your issue.
Google is a powerful tool but most of us barely scratch the surface when we use it. Here’s a good guide on how to start using Google a bit more effectively. Maybe that will help you get better results.
Before joining Treehouse, I was under the illusion that programmers knew everything off the top of their heads and rarely ever looked up stuff. I soon learned that part of being a real developer is Googling, constantly learning about things and looking things up. So don’t be afraid to keep searching till you find an answer, even if it takes you hours. The longer you’re frustrated, the more sweet the ah-ha moment is (to me at least).
Documentation is written with the explicit purpose of helping you navigate a language. It is the most direct source of information regarding a language and the environment you’re working in, but for a novice, it’s not super user friendly. We’re used to nice, well explained tutorials with hints and whatnot whereas the docs are straight to the point with barely any examples. It’s ok. Refer to it frequently and in time and with more use, you will be able to easily navigate your way around these dense documents.
Often times, a far easier way of getting information from the docs is to use Google, rather than reading the docs manually. If you want to find out how to append an item to a list in Python, you could manually sort through the documentation, which could take you quite a while, or you could Google “python list append”. The first result is all you need.
There are plenty of forums dedicated towards whatever you are learning. Spend some time looking through the archives for an answer. Again, you could do this manually, but Google is your best friend. One of the most popular (and my preferred forum) is StackOverflow. Usually when you Google a programming question, the top results are already from StackOverflow. But if for some reason you can’t find answers, just add the specific forum name to your Google query. In the guide I provided above, they indicate that you can use Google to search within a specific site. To look up all tableView related questions on StackOverflow, Google “site:stackoverflow.com iPhone UIAlertView”.
Probably the best thing you can do once you have some idea of what went wrong is to experiment. Learn by doing. Break things often and figure out what you went wrong. The beauty of programming is that it’s free to break things and free to keep going.
If you happen to have friends who are more than happy to help you (hello @bendog24 & @paradoxed) then use their time well, good help is often hard to come by.
If all else fails, then it’s time to ask the wonderful folks on the web. Asking questions in the right place can be one of the quickest ways to get your problem resolved, but a lot of novices can approach it the wrong way and get spurned. It is extremely important to write well thought out, clear questions that go straight to the heart of your problem. It’s not that these people get pleasure in reprimanding you, you just have to keep in mind that they’re helping you for free and if you waste their time with back and forth answers, they’re just going to get annoyed and leave you alone. Anyway, without making it sound any more dramatic, here’s a few tips on how to go about structuring your questions.
Before you pose a question, make sure you’ve gone through our first list and at least tried some or all of those methods. One of the most important skill sets as a programmer is the ability to work through a problem. By not trying to work out something on your own first, you’re giving the community the impression that you just want the answers handed to you, and this goes against their nature.
Given that you’ve tried to figure out things on your own, start your question by explaining what you’ve tried and what doesn’t work. Don’t talk about general high level problems, instead explain what exactly is wrong right away.
Context is very important. When you’re explaining your problem, don’t make people dig for information. Providing the context in which things aren’t working will allow someone to give you a direct answer rather than making them go back and forth for a while.
Post as much code as possible. I’ve seen plenty of questions where someone has to ask for the code before they can help you out. First, if you’re trying to solve a problem with your code, how can someone help you if you don’t provide said code? Second, take time to appreciate that these people are willing to hold your hand and patiently ask for your code. Don’t test their patience. 
If someone gives a very curt answer, don’t just assume they’re being rude and start writing up your annoyed response. It might just be that your problem has a very simple solution that requires a short answer.
Regardless of how someone delivers their answer, take the time to research it, try and implement it and figure out how it relates to your problem before asking for any more details. There are times when you just want an answer, but most times, being pointed in the direction is the best thing that can happen for your learning process.
Finally, ask nicely. On most forums, people are helping you for free. Don’t pester people if they don’t get back to you on time and don’t be bothered if they sound like the last thing they want to do is help you. Remember that it’s a person on the other end of the line, just like you and is taking up precious time to teach and help you. Be appreciative.
It took me some time to understand how to ask good questions and hopefully this should serve as a useful guide for those in the same place as me.
Reference material and further reading
The post Help, I’m Stuck appeared first on Treehouse Blog.
]]>The Division of Information Technology has been working with Turning Technologies to determine the optimum channel for clicker use so as avoid conflict with our campus wireless network, which was greatly enhanced this summer.
As a result of this review, please be advised that DoIT changed the Turning Point clicker channels on lecture hall computers on Friday afternoon, September 19. The new channel will be posted on the PC monitor and there will also be a sign facing the students. The channel was changed to reduce the possibility of RF interference with the system.
DoIT set the receivers in the lecture halls to channel 25 except ITE102 (LH8) which was set to channel 50. The reason for setting LH8 to a different channel is because of the proximity to LH7.
Instructors using their own receiver and laptop should select a channel between 74-82.
Turning Technologies has reviewed our recommendation and concurred.
Instructors:
To change/verify the channel on a computer (also found in Turning Point documentation):
1. Select the Polling tab in the TP software
2. The Receiver icon is located on the upper gray bar. If the PC channel does not match the posted channel, click on the icon.
3. Select the recommended channel. Laptop TP users should use a channel between 74 and 82.
4. Close the window.
Students:
To change the channel on a clicker (also found in Turning Point documentation):
1. Press the CH or Channel button (older response cards have a 'Go' button).
2. Enter the two digit channel for your location.
3. Press CH, Channel, or 'Go' again.
4. When the ResponseCard receives the new channel, the the light will turn green.
The reason for this change is that clickers use 1MHz channels within the 2.4GHz frequency band. On campus, we primarily use channels 1, 6 and 11 for wireless, which is occupied by the clicker channels 1-23, 26-48, and 51-73. To ensure that there is minimal interference, Turning Technologies recommends that devices are programmed on channels 24, 25, 49, 50, and 60-82.
More information from DoIT:
https://wiki.umbc.edu/pages/viewpage.action?pageId=41190437&src=search
https://wiki.umbc.edu/pages/viewpage.action?pageId=27297178&src=search
More information from Turning Technologies:
For questions or concerns, please contact AV Services (X52461).
]]>The Workforce Recruitment Program for College Students with Disabilities (WRP) is a recruitment and referral program that connects public and private sector employers nationwide with students and recent graduates with disabilities who are qualified and interview through the program.
This year they have decided to conduct phone interviews.The deadline to initiate the registration online is September 25, 2013. Deadline to complete the application is September 30, 2013. Phone interviews will be scheduled sometime between October 1st and October 18th.
To qualify for the program students must have 1) a disability, 2) be a U.S. Citizen, 3) be a current full-time student or have not graduated prior to December 2012 (unless the severity of the disability precludes the student from taking a full-time course load).
To be eligible to interview the student must follow the steps on the attached flyer.
The possible opportunities are for both full-time and internships for all majors.
The program is run on an annual basis (fall semester). Students who interviewed with the WRP last semester will need to reapply this semester.
]]>50 years ago, when UMBC was a being established, the administration did not lay any cement sidewalks. Instead, students created trails on the grounds as they found routes to their various classes and activities, and the University laid sidewalks on the students’ chosen tracks. It is in this democratic legacy, that we invite you to be a part of reviewing the paths past students laid for you as members of the UMBC residential community.
This August, the Residential Life Office began a review of the UMBC Community Living Principles. The 4 existing Community Living Principles were created by residential students 10 years ago as guiding principles for how we live and learn together as an on-campus community.
As we undertake the review of these principles, our charge is twofold: To work in collaboration with students to better understand what our community values, and who we become as a result of living these values together.
We encourage you to lend your voice to this process, by attending the focus groups on October 2nd and 3rd in your communities. Please also like our page on facebook, instagram and twitter using the links below, to get updates, and a chance to leave comments or participate in surveys. Visit our website: umbc.edu/reslife/living/CommunityLivingPrinciples to get updates on the process, and view the final draft when it is available.
Laying a new path requires work. Deliberate stepping to lay tracks in new terrain. Ultimately, those who created the path leave not only an easier way, but an expectation that others will follow in their footsteps. What path do you want to lay? What does your ideal community look like? Start the discussion here.
]]>|
|