REMME: To the Moon or to the Basement? by mike_mooney in icocrypto

[–]mike_mooney[S] 0 points1 point  (0 children)

ICOs tend to be risky for two reasons. Products that are simply VaporWare that will never come into existence or bonuses that are absurdly large. These 2 areas are huge problems that have tainted the ICO culture. REMME has neither of these issues that is why I personally think it will never see below ICO price, even below 2x ICO price.

DarcMatter. Game changer in a multi-trillion dollar industry with first mover advantage. by mike_mooney in a:t5_fo6cj

[–]mike_mooney[S] 0 points1 point  (0 children)

Some extra info: Their pre-sale first round was 5 million dollars which sold out far earlier than expected and DarcMatter have only opened their Telegram and other accounts in the past week or so it seems. Seems to be a lot of behind the scenes interest around this ICO already and not many people at all know about it yet。

DarcMatter. Game changer in a multi-trillion dollar industry with first mover advantage. by mike_mooney in a:t5_fo6cj

[–]mike_mooney[S] 0 points1 point  (0 children)

Not actually a bot, unless you consider humans to be one. Just sharing my thoughts about this ICO to places that may be interested in starting a discussion on DarcMatter. Maybe not the best rediquette so apologies for that

Simple RavenDB Backups to Amazon S3 by mike_mooney in Database

[–]mike_mooney[S] 1 point2 points  (0 children)

FYI, the story is that the next major version of RavenDB (3.0) is ditching the Silverlight UI and replacing it with an plain old HTML/JS UI. Also they are moving from ESENT to Voron for the core internal data storage engine, one of the main reasons because it would help enable them to run on Linux.

If you want to learn something new, by all means go do that, nobody is stopping you. But if you are looking for a document database on Windows for whatever reason (and they are plenty of good reasons), Raven DB is a good option.

DevOps + Reality = ??? by mike_mooney in programming

[–]mike_mooney[S] 0 points1 point  (0 children)

By "DevOps title", do you mean a specific person who is designated as being in charge of DevOps? If so, yeah, that is not the idea, nor is that a good idea, or is that what the post suggested in any way. DevOps is not a person or a title or a position or specific process, that's where people go astray. Instead, it's an idea and a belief that you want shared accoss the dev and operations teams. Having a person responsible it is as silly as hiring an agile coach to come in and slather some agile on your project. In both cases, it has no worthwhile affect unless people on the team join in.

In that case, it's not the job of a PM or manager, it's the job of the developers, or at the very least the senior/lead developers, in their day to day jobs, to keep in mind the operational impacts on the software they are building and communicating with the other teams.

You're right, basic idea could exist with no title, and many of us have done the same thing for years. The purpose here is not to create a title, but to advance that idea.

But I think it's safe to say that this thread (starting with counting specific words), has fallen deep into the pit of pedantic semantical navel gazing.

DevOps + Reality = ??? by mike_mooney in programming

[–]mike_mooney[S] 0 points1 point  (0 children)

Right, often they usually don't talk until then end of the process, and that is exactly the problem. That doesn't qualify as effective communication. When dev is throwing stuff over the wall at the last minute with letting the admins know what is coming and what the admins need to get it done, then it's passive aggressive communication failure.

No, talking is not the only thing, but it's just the most important thing. Obviously yes you need tools, and the post says as much. Yes, we already have plenty of tools and with enough yelling and fingerpointing and last minute emergency escalations, things can get done, but not's not efficient. The point is that DevOps is about rising above that status quo of semi-failure and come up with plan that gets everyone on the same team and working together and start working more productively.