Report
Share
Recommended
Recommended
EIS Smackdown 2012
The document provides information about sessions at the eMINTS Conference 2012 on using various digital tools for education, including online meeting tools, research tools, communication tools, media tools, and more. Over the course of 8 rounds, URLs and instructions are given for tools like TodaysMeet, Boolify, Remind101, RealPlayer, PhotoPeach, Present.me, ifaketext.com and ways they can be used for teaching.
Things I wished I knew while doing my tech bachelor / undergraduate
This talk is about how to use your bachelor to craft your tech career. I started with what I have done and some examples of where my friends have reached. Then I focused on things to consider for selecting and doing projects for technical subjects in bachelor study.
After that I opened up the secrets of selecting a company and doing internship. To concluded I gave some tips on approaching the job market.
Perlmania_Study - CPAN
This document discusses installing and using modules from the Comprehensive Perl Archive Network (CPAN). It provides instructions for downloading, extracting, compiling, and installing the Moose module from CPAN. It emphasizes that installing modules from CPAN is easy using the cpan shell.
Do You Git Your Code? Follow Simplified Gitflow Branching Model to Improve Pr...
Simplified gitflow has only one perpetual branch master which decreases the complexity, only one ticket can be deployed and tested in any given environment like staging or production. When only one ticket is deployed on a given environment, it is very easy to trace a problem if it occurs. As the full gitflow, master is the stable branch which can be deployed to production anytime.
Things i wished i knew as a junior developer
The document provides advice for junior developers from a senior software engineer. It recommends focusing on solving business problems over using the latest technologies, mastering programming fundamentals before complexity, and emphasizing clear and tested code over clever tricks. Non-technical skills like communication and timeliness are also important. Automated testing, logging, and monitoring help avoid bugs and allow for better sleep. Abstractions should be used judiciously as direct solutions may suffice. Overall development skills come from ongoing learning, practice, and experience rather than shortcuts.
More Related Content
Viewers also liked
EIS Smackdown 2012
The document provides information about sessions at the eMINTS Conference 2012 on using various digital tools for education, including online meeting tools, research tools, communication tools, media tools, and more. Over the course of 8 rounds, URLs and instructions are given for tools like TodaysMeet, Boolify, Remind101, RealPlayer, PhotoPeach, Present.me, ifaketext.com and ways they can be used for teaching.
Things I wished I knew while doing my tech bachelor / undergraduate
This talk is about how to use your bachelor to craft your tech career. I started with what I have done and some examples of where my friends have reached. Then I focused on things to consider for selecting and doing projects for technical subjects in bachelor study.
After that I opened up the secrets of selecting a company and doing internship. To concluded I gave some tips on approaching the job market.
Perlmania_Study - CPAN
This document discusses installing and using modules from the Comprehensive Perl Archive Network (CPAN). It provides instructions for downloading, extracting, compiling, and installing the Moose module from CPAN. It emphasizes that installing modules from CPAN is easy using the cpan shell.
Do You Git Your Code? Follow Simplified Gitflow Branching Model to Improve Pr...
Simplified gitflow has only one perpetual branch master which decreases the complexity, only one ticket can be deployed and tested in any given environment like staging or production. When only one ticket is deployed on a given environment, it is very easy to trace a problem if it occurs. As the full gitflow, master is the stable branch which can be deployed to production anytime.
Things i wished i knew as a junior developer
The document provides advice for junior developers from a senior software engineer. It recommends focusing on solving business problems over using the latest technologies, mastering programming fundamentals before complexity, and emphasizing clear and tested code over clever tricks. Non-technical skills like communication and timeliness are also important. Automated testing, logging, and monitoring help avoid bugs and allow for better sleep. Abstractions should be used judiciously as direct solutions may suffice. Overall development skills come from ongoing learning, practice, and experience rather than shortcuts.
Viewers also liked (7)
Things I wished I knew while doing my tech bachelor / undergraduate
Things I wished I knew while doing my tech bachelor / undergraduate
Do You Git Your Code? Follow Simplified Gitflow Branching Model to Improve Pr...
Do You Git Your Code? Follow Simplified Gitflow Branching Model to Improve Pr...