Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
sleepycal
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
Psychedelics For Your Software Engineers
(nearshoreamericas.com)
2 points
by
sleepycal
7mo ago
|
0 comments
2.
▲
This is what happens when your 3yo realises you forgot to lock the server rack
(twitter.com)
2 points
by
sleepycal
9y ago
|
0 comments
3.
▲
by
sleepycal
11y ago
It's actually coming in about a week or two. I wanted to do it on 17th (exactly 1 year after) but needed more time to work on it. No spoilers, I don't want to the ruin the surprise :)
4.
▲
by
sleepycal
11y ago
Nope, their role could be easily removed by technology. Internal hirers are required, recruiters are not
5.
▲
by
sleepycal
11y ago
I'd like to hear more on this, have you raised the question on Reddit too?
6.
▲
by
sleepycal
11y ago
Honestly, I've had to endure countless terrible recruiters/agencies, to the point that I don't even pick up the phone unless they have been referred by word of mouth - or if I really need the cash ;) And 9/10 times, th
7.
▲
by
sleepycal
11y ago
Interesting read. It's about time that recruiters are put in their place, the majority are lazy/untalented yet they take 20% cut. It's not right :X (Disclaimer: I'm biased).
8.
▲
Over 9000 vulnerability POCs, hand delivered on camera
(iops.io)
5 points
by
sleepycal
11y ago
|
1 comments
9.
▲
by
sleepycal
12y ago
Although this comment seems to be more focused on baiting, rather than constructive criticism, it points out that I have failed to justify my comments about Docker registry being overly complex, though I addressed this in another comment [1
10.
▲
by
sleepycal
12y ago
Thank you for the honest feedback, this is the first post I've seen arguing the technical aspects of the article, thank you. > The strike-out font was a nice touch, man I've made it clear in other replies [1] that the comment w
11.
▲
by
sleepycal
12y ago
Just wanted to say a huge thank you to everyone who has taken time to reply, the response has been overwhelming! There's still many comments I'm yet to reply to, and will finish replying to these tomorrow evening, but it's no
12.
▲
by
sleepycal
12y ago
Configuration manager, such as Puppet, Chef, Salt Stack etc.
13.
▲
by
sleepycal
12y ago
Although I would agree that services such as EC2 are not cost effectively for 1:1, this argument is somewhat invalidated when you consider $5 instances from DockerOcean. $100/month for 20 concurrent VMs is enough to replicate even the
14.
▲
by
sleepycal
12y ago
I'm glad you replied, as it wasn't intended to be arrogant. Some people care about the end result, not worrying about how it gets done, as long as it's done. Others care about the journey, perfecting their art at every stage,
15.
▲
by
sleepycal
12y ago
I'd be inclined to agree that my story was incomplete, something which I addressed in another comment [2], and I have made some amendments over the last few hours which give fair reference to the positives of the Docker ecosystem. Howe
16.
▲
by
sleepycal
12y ago
Heh, I wasn't aware of that. Thanks for the heads up, I'll digest properly tomorrow!
17.
▲
by
sleepycal
12y ago
I would have to strongly disagree with this, not just because AWS has been capable of doing this for quite some time, but also because of my own success stories. I'm due to post a follow up article, explaining the pros/cons of the
18.
▲
by
sleepycal
12y ago
Thank you for your honest feedback, I do really appreciate it. You've raised the same point many others raised, and it's important to note that my argument of uselessness is from the specific standpoint of daily, long term usage o
19.
▲
by
sleepycal
12y ago
Thanks for sharing, I've seen appc mentioned in a few comments, I'll check it out properly tomorrow. You also raise a good comment about blindly trusting containers which, despite having concerns about this in the past, regrettabl
20.
▲
by
sleepycal
12y ago
Thanks, my bad. SmartOS has been in my todo list for a while now, along with CoreOS, they both look very interesting.
21.
▲
by
sleepycal
12y ago
Thank you for the feedback. Although the README looks slightly easier than previous, it still makes for difficult reading, and I'd argue that they need to document this better. Unless you have a link to somewhere this has already been
22.
▲
by
sleepycal
12y ago
Thank you! I've heard good things about Core OS, looking forward to trying it in the lab.
23.
▲
by
sleepycal
12y ago
Although I haven't yet reviewed LXD, I agree that plain LXC is an absolute pita to use, at least it was in 2012 (the last time I used it in prod, aside from Docker)
24.
▲
by
sleepycal
12y ago
Interesting, I hadn't heard of HTCondor before but have recently become more interested in bioinformatics, which seems to use this quite a bit (at least in Cambridge). I'll have a read, thanks for the heads up :)
25.
▲
by
sleepycal
12y ago
Thank you for your honest thoughts, I respect that. I've updated the article to reflect the comments that yourself and many others have made, and you're right to call me out on it. You are right that I've failed to justify my
26.
▲
by
sleepycal
12y ago
Thank you for the feedback, that's actually quite an interesting use case of the Docker ecosystem. I've already updated the article to reflect this, as you raise the same point that many others made. (copy) "However it's
27.
▲
by
sleepycal
12y ago
Vagrant certainly has it's own problems and frustrating bugs, in fact I outright refused to use it in the early days. There is differing opinion on "the right way", depending on what your priorities are. Mine are based on pre
28.
▲
by
sleepycal
12y ago
I'll check out MirageOS, I've also heard some interesting things around CoreOS, which I'm hoping to get some lab time for soon. Finding time to review everything properly is difficult, this article was the summary of 6 months
29.
▲
by
sleepycal
12y ago
Thank you for your honesty. Although I stand by my comments of Docker being unnecessary, I would agree that my "If you expect anything positive" comment is wrong. This has been pointed out by other people as well, and I'm goi
30.
▲
by
sleepycal
12y ago
> Also these VM images usually contain tons of undocumented "state" Although I agree this approach is absolutely flawed, and anyone doing so needs to re-evaluate their workflow, I feel this comment is more an argument of doing
More ›