839 karma · joined December 5, 2013
It's sometimes tough to dissociate the problem with the people involved. Hope this will have a positive resolution as most of the people seem to be experts at what they do.
I love Nomad's flexibility and ease of use, a simple hcl file and I (and all the devs) can debug and understand what is going with the deployment without wasting a whole sprint, debugging and understanding the systems is trivial. However I agree parts of the documentation should be fixed and can confuse people who want to start up and it's also relatively "new" insofar that there is a small but growing community around it. I love Kubernetes because of the community, if there's a Helm chart for a service, it's going to work in 80% of the cases. If however there are bugs in the helm chart, or something is quite not on the beaten path, then good luck. Most of the time wasted on Kubernetes was the inexperience of the operators and also the esoteric bugs that can happen now and then. Building on top of things that have been done before is a great way to win time and flexibility but it shouldn't be an excuse to not understand them (helm charts as an example).
In both cases, you always need an ops team to take care of the clusters. For Nomad, 2/3 people are enough. For Kubernetes you will need 5+ people depending on the size and locality of the cluster, if you want to do things right, that is. If your dev team is managing them it's already game over and just a question of time until you made yourself more real problems than you initially had.
What bugs me the most however is the cargo culting around the tools serving as a "beating around the bush" technique to not do actual work. They're just that, tools, if you have to deploy a rails or django app with an sqlite database just do it on metal with a two liner "ci/cd" and grow from there. If it gets bigger, sure, go for Kubernetes to manage the deployments and auto scale, but be damn sure that you can debug anything that goes wrong within minutes/hours. If things go wrong and there's no hit on your googled error code you essentially fall from your highest level of abstraction and are at the mercy of consultants that will both waste your time in writing requirements and waste your money by taking too much time than was initially planned and agreed upon (my experience, sample size N=6).
<img src="https://api.assetroulette.com/random_meme?hello=there"> <img src="https://api.assetroulette.com/random_meme?general=kenobi">
Should give two different images on the same page :) I think it's because of how the browser caches a request for the same url but I don't know exactly yet. :/ I will definitely implement the search part, that is a great idea! Thanks again.
You're right, I'll check into the AI generated images, I currently have a pretty beefy GPU machine at home that I was searching a use-case for :)
Since last year I developped many websites for friends that wanted either to start working on their own or just wanted to have a small online presence. While designing I always had problems finding the right pictures / images / stock or design inspiration to get them going so I whipped out a small free project to help me "randomly" find images https://assetroulette.com/.
You can try it out, it's free, no need for registration, I am not gathering emails or whatever, it's so far just a simple tool I whipped up last weekend to solve a small niche problem I had.
Currently hosted on a 3€/month server. It helped me visualize images in their context (web page) to iterate quickly. The issue I was facing was that while some images on stock websites looked cool at first, embedding them almost always looked bad and was a waste of time... This way I can refresh a couple of times and eventually find an image that is relevant (works for CSS too and generally any asset - even user provided ones - on the webpage that can be shuffled until it is satisfactory).
I'll leave the website up for a little. I decided to share it because I successfully used it today on a website for a friend that wants to start selling jewelry. I would love to have some feedback, it's still in construction but maybe you can already find a good use of it. Thanks in advance!
We are looking for new colleagues that can help us design and build software stacks for the next-generation in-vehicle data collection, aggregation and machine learning systems. We are a central team with solidly growing visibility within the company. Feel free to contact me any time if you have a question. I am personally involved in the recruiting process as project lead for all the backend activities. We use a modern stack, modern tools (Kubernetes, Nomad, Terraform, multi cloud deployments, Python/Pytorch, C++/embedded, OTA & co...) and we have nice cars with a competitive compensation package :) For any questions please feel free to reach me at karim.jedda@audi.de with the title "HN: Who is hiring?" or on https://www.linkedin.com/in/karim-jedda/ if you don't want to share your email.
To apply directly:
Senior Python Software Engineer: https://recruitingapp-5052.de.umantis.com/Vacancies/1943/Des...
Senior Data Engineer / DevOps Engineer https://recruitingapp-5052.de.umantis.com/Vacancies/1942/Des...
Senior Data Scientist https://recruitingapp-5052.de.umantis.com/Vacancies/1888/Des...
Senior Software Engineer focus Perception-Machine Learning https://recruitingapp-5052.de.umantis.com/Vacancies/1887/Des...
Senior Software Engineer C++ focus Intelligent Data Aggregation (m/f/d) https://recruitingapp-5052.de.umantis.com/Vacancies/1886/Des...
Put like this it makes a whole lot of sense now, I was maybe just distracted by the examples the author brought in which confused me. It really shows that there's a spectrum of possible ways on how to deal with rejection that I am not aware of.
I never took rejection personally but in contrary saw it as a challenge. Maybe that helps to frame why I wrote my initial question. I agree that it's tirening to have to work twice or 3 times as hard as others for the same result and having more roadblocks on the way (metaphor for rejection) but one thing that is sure to me, I never really gave any importance to emotional rejection because that one is very subjective and I don't understand why people think how they think. I might lack the emotional intelligence?
The one that might have challenged me the most was rejection at work or rejection for just having a foreign name or foreign face because the latter is a checklist with all the marks ticked but still, something didn't quite fit completely.
Thank you for clarifying though, I get it, I definitely had a different definition of what a rejection is which is what caused my confusion.
For the last part, I absolutely agree, some people tend to be too focused on the rejection itself and define themselves by it instead of doing something to changing it or themselves. Which always leads to bad things.