Explore >> Select a destination
|
You are here 
|
www.laac.dev | ||
| | | | |
benoitpasquier.com
|
|
| | | | | For the past few years, I had the opportunity to mentor new joiners through different roles. In some aspects, I could see myself in them the same way I started years back: eager to prove themselves, jumping on the code and hacking around. I tried to think about what I learnt the hard way since my first role in the tech industry and how could I help them learn the easy way. | |
| | | | |
www.hillelwayne.com
|
|
| | | | | Caveats: Im not an interviewer, Ive never done serious research on interviews, and I havent tested this. I propose this entirely as a thought experiment. Assumptions: We interview at jobs to find ideal candidates. WE are looking for candidates who are Good at programming Good at software engineering Can work in a team A culture fit (not an asshole). Technical interviews test the first two. They are primarily whiteboard questions, abstract design questions, or write this program questions. | |
| | | | |
www.e4developer.com
|
|
| | | | | In my career as a software developer, I have interviewed over 100 people. Most of these interviews were face to face interview involving coding on paper or a... | |
| | | | |
www.softdevtube.com
|
|
| | | Computers are orders of magnitude faster than when most of us started programming and yet a lot of software runs much slower than it should. Nobody likes progress bars. Slow code provides for a horrible user experience, drains batteries faster, and increases our cloud bill. This session explores some of the reasons why software is | ||
