pedoh
Joined 16 years ago
Joined 16 years ago
Also, would it be malicious if the author had simply deleted the project altogether, as opposed to putting in an infinite loop? From the author's perspective, if you want to use my code, fork it, and have at it, but I don't want it in my space any more. Is that not a reasonable stance to take? It may not be the "right thing to do", but it is his code, and he is the associated "owner" of the code. I don't know.
Going to an extreme, the implication _could_ be that I should never delete any open source project that I create, because it would be "malicious". The reality is that I could delete most of my open source work, and nobody would bat an eye. I'd be pretty shocked to my doing that being labeled a malicious act.
One piece of feedback, I couldn't discover in the app itself how to make references to other documents. I finally figured it out by looking at your web page and seeing the [[connections]] bit.
raycast ticket create "Run database migration in production"
raycast ticket<tab>
create claim set_owner close
raycast ticket set_owner p<tab>
I've written a tool that uses a plugin system to easily add more "commands" to be run. I haven't tackled the tab completion piece yet, but I can imagine that it would significantly benefit the user experience.I am the hiring manager for a DevOps Engineer at Juvo. I'm building out the team (currently a team of me) as our trajectory keeps going up and to the right. One of our big projects this year is getting our infrastructure running outside of AWS due to country privacy laws. In particular, I'm looking for three areas of expertise (you do not have to have experience in all three of these areas):
1) Configuring and administering Containers / Docker / Kubernetes.
2) Installing, configuring, and administering some of the following: Hadoop / Hive / HDFS, RabbitMQ, Kafka, Memcached, Redis, PostgreSQL.
3) Networking experience, including configuring and administering VPN connections with external partners using software like strongSwan.
We're in San Francisco in the Financial District, looking to hire locally with an eye on remote as we grow, so an exceptional remote candidate may be considered.
Apply online (https://juvo.com/job/devops-engineer/) or contact me via email ([email protected]) for more information.
We're hiring in a lot of areas, but I'm focused on Site Operations, where I'm the principal engineer.
Our application stack is based mostly in Java, however most of our operations automation is developed in Python. The major components we use daily are Ubuntu/Linux, MySQL, Redis, Neo4j, Solr, logstash, Kibana, Graphite, collectd, StatsD, Nagios, Tomcat, Fabric, Jenkins, Git, JIRA, Confluence, Stash, Cassandra, Puppet, HAProxy, Nginx and Ansible. We leverage mostly externally hosted bare metal servers, with some virtualization thrown into the mix.
Feel free to contact me (Fitbit email in my profile) with any questions you have.
It looks like they're not leveraging LXC via Docker. I wonder if that's because they've been doing it this way pre-Docker, or if there are some technical reasons why it made sense to skip it.
https://help.fitbit.com/customer/portal/articles/854753-mana...
Gitolite is gone, long live gitolite?
I have a few suggestions.
Make the code easily copyable. Under Chrome, at any rate, if you select the code you can't help but select your comments to the left of the code. I think that people running through the examples should type everything in line by line, but some people will prefer to copy and paste.
Also, it would be great to have some "where to go from here" links. I've run the examples, now I want to write some useful code. Where should I go next?
[ my public key: https://keybase.io/pemerson; my proof: https://keybase.io/pemerson/sigs/J8SHgVev_9m8GkFZwNUGVtk6-gaQx4ma4nuyPxurwx0 ]