News for hackers. Stuff that matters.

remmelt

Re:Ask HN: Who wants to be hired? (June 2018) on Saturday June 02, 2018 @04:04AM (#17213403)
I'm looking for contracting work.
Re:Ask HN: Who wants to be hired? (June 2018) on Friday June 01, 2018 @05:17PM (#17210413)
Senior Tech Lead / Senior DevOps engineer / Senior Software engineer

  Location: Amsterdam, The Netherlands
  Remote: Yes, but prefer onsite
  Willing to relocate: No
  Technologies: DevOps, Software Architecture, Openstack, HashiCorp stack, Salt, Ansible, Java, Go, Spring, Cassandra, Kafka, Docker (Certified Trainer)
  Résumé/CV: cv.remmelt.com
  Email: [email protected]
  Languages: Dutch, English
Senior software engineer, strong DevOps and programmable infrastructure experience. Built and architected large scale web applications, online auction, messaging platform. I love building software, but I love even more to build bridges between people, and teams.
Re:GitHub commit search: “remove password” on Wednesday February 15, 2017 @07:00AM (#13651384)
Continuous development, e.g. Jenkins? (Please don’t do this)
That would be something I'd pay money for.
Re:Ask HN: What book have you given as a gift? on Monday August 08, 2016 @06:52AM (#12246721)
Cooked by Michael Pollan.

Great history about food, how cooking made us "human," links to religion, feminism, consumerism, and much more. Very insightful and at times heart felt. Not recommended if you don't eat food.

This stops short at all the really interesting stuff of microservices. Where's the service discovery? Failover? Secret storage? Communication?

Besides that, I don't agree with putting dependency injection in a microservice. Why bother? In a sense, microservices are a breath of fresh air, because they're supposed to "fit in one developer's head." If you're already adding layers of indirection, you're making the code harder to reason about for no good reason.

Re:Why we ditched Django for Microservices on Monday January 12, 2015 @10:32AM (#8874349)
There are two sides to this.

Technically, one way of solving this is to make sure that the acceptance criteria for any single micro service are clear. For example, you have to expose these REST endpoints; given data set A, respond in this way to these requests, etc. To me, a micro services architecture implies that the development team is responsible for the entire life span of the service, from conception to replacement. This includes maintenance. Insert the devops buzz here as well. When the given solution can no longer be maintained because of failing knowledge (or even interest?) by other devs, it should be replaced. This should be no harder than refactoring a large method, except on the scale of an entire service.

Non-technical benefits include expanded responsibility and shiny architecture can possibly attract better developers/engineers. I know this has worked for us.

I think it would be reasonable to somewhat limit the available choices, especially at the start of a project.

Re:Homemade Speakers on Sunday July 06, 2014 @05:42AM (#7994135)
I'm very interested in the Arduino based pre amp. Do you have a page with your design that I can study? I was thinking about maybe integrating a Lightspeed Attenuator.

Most of all, I'd like the pre amp to automatically turn on the power amp (currently a Gainclone) when a signal starts coming in from the connected Airport Express.

http://diyaudioprojects.com/Solid/DIY-Lightspeed-Passive-Att...