kaesve
Joined 11 years ago
Joined 11 years ago
(We'll get back into 3d printing once life slows down a _little_ bit again)
Location: Philadelphia/New York
Remote: Possible
Willing to relocate: No
Technologies: Python, TensorFlow, PyTorch, JS/TS, NodeJS, Angular/React/Vue
Résumé/CV: https://hireken.at/hacker-news/
Email: [email protected]
I'm a software dev with 10 years of experience in full-stack development in JS, TS, Python, and Java. I recently received my MSc in Data Science and Machine Learning, and am now looking for a new challenge.I enjoy reading up on computer history, and this is a pretty good retelling of an important story. However, the parts that really struck me are the personal accounts of the author in trying to recover this history. The ENIAC 6 played an important role in the history of the first computer and of programming as a vocation, but their story was almost forgotten. To the point that these women were not even invited to celebrate the 50th anniversary of the ENIAC. That's shameful, and I'm happy that they finally have started to get the recognition they deserve.
If you're interested in this history, Jean Jennings Bartik also wrote an autobiography, that tells the story from her perspective.
Location: New York/Philadelphia
Remote: Yes
Willing to relocate: No
Technologies: Python, Tensorflow/Torch, Javascript/Typescript, Node, Angular/React/Vue, Docker, SQL
Résumé/CV: (working on it)
Email: [email protected]
Software engineer with ~10 years of experience. Most of that in front-end and full stack, but I recently went back to university for a MSc in machine learning. I'm a team player, and I love helping to solve real world problems.I'm from the Netherlands, but moving to the US (Princeton) soon, and should have my green card by the end of the year, so I'm looking for something new.
I'd love to find a new challenge in the ML field, but I'm open to other opportunities.
I really enjoyed reading the latter last year, because it does a great job slowly building up. By the end, I felt like I didn't just understand the models, but also how the author found them. I can recognize these patterns in nature, and figure out how they were generated.
I spent some time last year implementing all the models described in the book in JS: https://kaesve.nl/projects/shells .
It also teaches you more about your platform. In the end, all these web tools and frameworks are running in that same browser. I find especially with newer web developers, it's hard to solve something in React/Vue/.. because they don't know how to break up the problem. If you'd roughly know how to solve the problem without those frameworks, it becomes much easier to figure out how to solve it with them too.
Finally, I also just get toolchain fatigue. If I want to build a simple landing page, I don't want to learn new stuff, I don't want to read what changed in the latest versions, what the correct way of the day is to set up a project. Honestly, I don't even want to have a build pipeline and module swapping dev server, that inevitably needs to be configured. Just some static html/css/js is often good enough. And as I said, you also learn which problems frameworks solve well, so you'll know when some static files isn't the right choice.