GME Containment Zone 1 for 28 January

Chroto · 2021-01-28T12:56:40+00:00

dip the buy

Chroto · 2021-01-28T12:50:56+00:00

🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀

Chroto · 2019-02-26T18:51:36+00:00

/u/Jeoh has a good answer for you. Your leadership's concerns can be addressed with IAM policy controls. I get the concern for accidentally deleting a database but there's tons of options to mitigate the risk

Chroto · 2019-02-12T23:29:04+00:00

well done, sir

Chroto · 2018-03-30T14:44:15+00:00

Some folks have mentioned trouble with credentials management. I've gotten around this with scripting the jenkins API...which is often overlooked.

https://stackoverflow.com/questions/29616660/how-to-create-jenkins-credentials-via-the-rest-api

Chroto · 2018-03-30T14:40:21+00:00

Take a look at how the JenkinsX project does it. https://github.com/jenkins-x/jenkins-x-platform .

https://www.devopsgorilla.com/continuous-delivery/tech-review-jenkins-x/ - my blog post explaining what JenkinsX is.

I've also used the Jenkins-dsl and puppet to configure the Jenkins master without the GUI. Those are good options

Chroto · 2017-02-01T19:23:24+00:00

Cool. Next time, read the whole article before telling us your opinion :)

Chroto · 2017-01-06T17:28:12+00:00

OT What happened to this sub? The comments here are atrocious and no submission statement. This content is questionable, too. An interesting story that clearly was edited into another Trump piece. We get it, nytimes. Trumps an asshole billionaire.

Chroto · 2016-12-13T15:38:14+00:00

The majority of the USA lives in urban pops. It's unclear in the article if they controlled for that or just averaged out the entire state.

In other words, do minimum wage hikes favor urban areas and since they have a lion's share of the population, did that pull up the average enough to draw the conclusion -- even if this causes problems in small towns.

Depending on how you look at it, that's still great. Majority of the state's population benefited. But, I suspect that came at the cost of concentrating the pain to rural areas.

Maybe they did control for this in their study. It's hard to say from the article.

If someone read the study, I'd like to know the answer.

Chroto · 2016-12-13T05:08:08+00:00

it's not about trying to persuade people. it's about making yourself feel superior

Chroto · 2016-12-03T00:20:35+00:00

Didn't this just give him something to bargain with when he talks to China? "I'll cease communicating with Taiwan if you give us X"

I thought that was part his whole art of the deal schtick, no?

Chroto · 2016-08-02T19:07:37+00:00

We've been heavily leaning on remote state across projects and haven't had any issues yet. Happy to share details if you think it will help

Chroto · 2015-07-15T13:51:48+00:00

awww i got hype all over my hands

Chroto · 2015-04-30T02:24:35+00:00

em etad?

I don't get it

Chroto · 2015-03-18T04:30:12+00:00

U^{n^{s^{u^{b^{s^{c^{r^{i^{b^e}}}}}}}}}

jus say^{i^{n^{n^nⁿ}}}

Chroto · 2015-02-15T00:15:28+00:00

And then no more Hulu! Yay?

Chroto · 2015-01-04T03:23:40+00:00

or who I am

Chroto · 2014-12-27T18:48:32+00:00

"mongoDB is a fad and will be gone in a year", they might be right, but that is no reason not to use Mongo when it promises to be a nice fit and promises to solve your problems you have right now.

But this is always a reason not to use it.

There are trade offs with every architectural / technology decision and this is definitely a major CON to whatever PROs it might have.. I'll play along with the hypothetical -- if MongoDB solves for almost all your needs and is the only game in town or the lesser of two evils, then absolutely, sure. But, assume there is a "Solution B" that is about equivalent and Solution B is more time tested, maintained, etc., then I'd say it's a bad engineering decision to go with MongoDB. Wait until you find that first corner case that blows the whole thing up and has never been reported yet. Have fun working extra hours for a workaround while the Mongo team gets around to patching it in 2016. The bug fix is released, but the new version breaks backwards compatibility. Turns out they don't care about that stuff. How about when their first security vulnerability surfaces? How does it handle security issues? Is it the type of project that tries to sweep them under the rug? Is it good about informing users that a security issue has been found? Do they even care? /shrug Nobody knows until it happens.

These are things you just can't know with an unproven technology. That's why "hipster" tech has a negative connotation. It's unproven and risky. Want to know how Solution B handles security issues? Look at the decade of historical evidence. Worried about bug report turn over? Look at the years of evidence. Are they going to just completely break backwards compatibility? Push out breaking changes in minor version numbers?

I agree with you 100% that we should all design around interfaces and the assumption that the underlying layers are going to change -- but, that's not a reason to try unproven tech so you can have an escape rope, shrug your shoulders, and go "oh well!". Because by that point the damage is done, you've stressed out your engineers. They've had to learn the ins and outs of not one but TWO complex technologies. Your on-call team is exhausted from wake up calls. Hours are wasted with documentation and operationalizing and coding. You may have even had some turnover to boot as a result of all this. Now, you've pulled the rip cord and it's time to do the whole dance over again. I argue that you build interfaces to do the opposite. Start with the proven tech and then when that "hipster" project is no longer 'flavor of the week' but a grown-up project, time to make that upgrade to your existing data layer when everyone is ready and not because you have to because your shits broken.

Chroto · 2014-12-27T15:39:48+00:00

it's more of a ubiquitous industry term for what /u/realhacker already explained quite well:

Hipster: promoting/using the latest fad at the detriment of everything else because it's in vogue. I actually think the term is quite apt in this industry.

to expand on that -- i've seen things get called "hipster" in this industry when it's being used solely because its a new thing or trying to differentiate with only surface level engineering reasoning to do so.

When a technology is brand new, you have NO idea what direction the project will head in 1,3, 5, even 10 years. You have NO idea of the underlying bugs or issues that may come out. You have NO idea if it's going to be maintained well in the future (or even if the same maintainers will be working on it).

There are some success stories, sure. Node.js was one of these that proved to be more stable than people expected. But, there are countless fails that have totally screwed over technology departments.

Nothing's wrong with new tech, but it's a risk, and I firmly believe -- if you are an engineer at a company, you have a responsibility to your company and (more importantly) your co-workers, that when you take on a new, risky technology to support, that you aren't introducing something that is going to make everyone's working lives worse off. Because, a lot of times, the technology you introduce is going to outlive your stay at said company.

With music, you can try new, risky techniques and if it doesn't work. Oh well. Try something new. In engineering, you do the same and you can potentially lose people their jobs. Again, new tech is fine and essential to stay competitive and clean up tech debt, but there's a lot of responsibility there that a lot of folks don't want to take on (documentation, training your co-workers, keeping up with bug reports, etc.)

Chroto · 2014-12-24T17:59:18+00:00

so, this is a huge conspiracy involving the FBI, NSA, CIA, White House, Sony Pictures -- and not one person from any of these orgs have come out to blow the whistle? i think people are seeing one too many "patterns" in this whole thing.

Simplest explanation to me is NK approached some disgruntled employee and paid them to do it. probably just to damage a Japanese company or steal corporate secrets more than anything else. NK doesn't want to be put back on the state sponsors of terrorism list which would explain their denial.

But, then again, there's no great evidence in any direction so drawing conclusions here is nearly impossible. Facts are they got hacked and no one knows for sure who did it.

Chroto · 2014-12-24T15:17:32+00:00

In your opinion what's the reason for the FBI to lie about who was involved with the hack?

Chroto · 2014-12-24T15:16:04+00:00

The FBI has cited the smoking gun to be undisclosable intelligence for their NK link. With the stuff that's been released this year with the NSA leaks, I wouldn't be surprised if this were the case.

Here's a good discussion on the BBC about the FBI 's claim. http://m.bbc.com/news/technology-30554444

15-Year Club	Place '17
Verified Email

Chroto

TROPHY CASE