distracteddev90
Joined 12 years ago
Karma
56
Submissions
32
Member since
Feb 20
Recent submissions
Comment · 2 years ago
Does this work well when set up to use my local machine and my personal credentials?
Comment · 3 years ago
Not the original commenter but I manage a similar system:
1. Wait timings for jobs.
2. Run timings for jobs.
3. Timeout occurrences and stdout/stderr logs of those runs
4. Retry metrics, and if there is a retry limit, then metrics on jobs that were abandoned.
One thing that is easy to overlook is giving users the ability to define a specific “urgency” for their jobs which would allow for different alerting thresholds on things like running time or waiting.
Comment · 3 years ago
Was affected by this, and so far, windscribe is a far superior service.
The transition was seamless.
Comment · 9 years ago
Just signed up and this is almost exactly what I've been looking for.
The Github repo mentions a REST api that can be used to push arbitrary data into the system. Are there any docs around this yet?
Comment · 10 years ago
There is no reason to feel alone, perhaps rare, but not alone. There are others that share your feelings (including myself).
These people are often labelled as the "pragmatic". They also lean towards having a more general scope of knowledge and thus often lack a "speciality".
There are also those that simply wish to solve the problem in the "best" way possible, and will use whichever stack gets them closer to that ideal solution.
disclaimer: purely based on my experience/opinion/perspective.
Comment · 10 years ago
Turning off javascript also removes most paywalls, even the ones that have started protecting against direct links from search results.
Comment · 10 years ago
I believe this is symptomatic of an industry moving away from job board based recruiting. There has been a significant change in the recruiting sphere and many talent teams are starting to focus more on sourcing and pursuing passive candidates.
Comment · 10 years ago
This is the exact situation I'm in and I'm on my 3rd TN. Get a good lawyer and this shouldn't be a problem.
If you do get this visa though, be very careful what you say to the border guards. You need to ensure that when speaking about your work, you always frame it as "work in support of scientific research/innovation".
Comment · 10 years ago
The main premise in my comment is that the benchmarks do not resemble real world performance, and are therefore misleading.
The comment above (https://news.ycombinator.com/item?id=11626762) further expands on why these kinds of benchmarks, although interesting, have no real value.
Each implementation does something wildly different and responds to different inputs with completely different outputs.
To put it metaphorically, if you put a car engine in two completely different chassis and then race them on a track, you aren't gaining any real insight into relative performance of the engine in the two vehicles.
Also, just to be clear, my qualms are with the benchmarks alone, I think the library is great! Thanks for all the hard work :)
Comment · 10 years ago
The benchmarks for node.js are terribly misleading. The node.js implementations only ever spawn a single process, and thus node is only running on a single core and uses only a single thread.
Specifically, the http server example(1), doesn't even bother using the standard library provided Cluster module(2). Cluster is specifically designed for distributing server workloads across multiple cores.
All node.js services/applications I've worked on in the past 3 years (that are concerned with scale) utilize a multi-process node architecture.
The current benchmark can only claim that a single python process that spawns multiple threads is 2x faster than a single node.js process that spawns only one thread.
This fact may be interesting to some, but is irrelevant to real world performance.
[1]: https://github.com/MagicStack/vmbench/blob/master/servers/no...
Comment · 10 years ago
One thing I find interesting is that everyone loves to hate CoffeeScript, but its individual features/syntax are consistently lauded in conversations about other languages.
(Not to mention half of ES6 existed in CoffeeScript first, but that's a gripe for another day)
Comment · 11 years ago
Docker doesn't force you to put your app and your db on the same image. That is up to you. Most have "App" images and "DB" images separate.
If we want to get really specific, Its also common to see the "DB" image split up between the image of the disk where the data is actually persisted, and the image of the actual DB process. This makes it easy to play around with your data under different versions of your DB.
Comment · 11 years ago
Hrmmmm good point. Not one that applies to me particularly since if I'm on a server then I'm usually only running pre-written .sh scripts.
(edit: this was a reply to the post below.. not sure how I messed that up.. gah.. such a noob)
Comment · 11 years ago
Would you mind expanding on what fish does out-of-the-box that prezto neglects or hides behind configuration? I am in a similar boat as you and was just wondering what I had to look forward to as a prezto user.
Comment · 11 years ago
I can clearly see the difference between Fish and regular ol' bash, but struggling to see what value Fish adds above prezto/zsh. Could anyone help me out here?
Socials:
https://bsky.app/profile/distracteddev.bsky.social
Interests:
AI/ML, Entrepreneurship, Fitness, Hacking, Hiking, Investment, Programming, Research, Startups, Writing, Yoga
---