/explore
|
You are here 
|
wittchen.io | ||
| | | | |
trishagee.com
|
|
| | | | | Last week (was it only last week?) I was at Strange Loop, presenting a workshop on the Disruptor. I didn't really have any expectations from the conference, I've never been before and, if I'm honest, hadn't heard of it before. So everything was a pleasant surprise. It's a very geeky conference. I mean that as a compliment, of course. Lots of very smart people talking about stuff that's waaaay more advanced than you frequently get in the conferences employers would be happy to pay for. The themes I mostly saw were functional programming and the (insert horribly abused term) Big Data space. | |
| | | | |
dylanpaulus.com
|
|
| | | | | A few months ago I had an opportunity to give a presentation to soon-to-be Computer Science (CS) graduates. We presented the software development process (), and how different teams at Schweitzer Engineering Laboratories adapt the development process to their needs. We ended the presentation with ti... | |
| | | | |
duksta.org
|
|
| | | | | The talk I gave about streamlined vendor review processes at Art into Science: A Conference on Defense 2020 | |
| | | | |
www.susanjfowler.com
|
|
| | | In today's post, I want to share some of the things I've learned about how to structure and run these types of interviews. If you're here because you want to know how to ace the architecture interview, you should keep reading, because I think the best ways to prepare for these things is know how interviewers think about them. | ||
