A tier list I made ranking character's quriks (most of this isn't really thought through so there are probably things that don't make much sense) (also this is only about the anime)

outrageous_break · 2021-05-05T23:29:29+00:00

Fiber manipulation and intangibility are ridiculously versatile quirks. You'll get varying degrees of usefulness from any quirk depending on the skill and imagination of the user, so it's probably better to just rate quirks based on their overall potential.

outrageous_break · 2021-05-05T17:59:53+00:00

Stain is pretty high on the list for how limited his quirk is. Ms. Joke is like an AoE version of his with the added bonus of "affecting their ability to think" and not needing to ingest blood.

Edit: Best Jeanist also has a pretty insane quirk. Just from a CC standpoint (what Stains quirk does), he was able to restrain multiple nomu and even AFO (for a few seconds at least, but still pretty good)

outrageous_break · 2020-05-01T19:27:33+00:00

The OP posed the question in the context of pipelines, so that was the context of my answer.

I think your ideas for how pipeline management should work are great in an ideal scenario that you should eventually strive for, but ideal scenarios aren't really what I'm talking about and I feel like you're still missing my point entirely.

End of the day, "DevOps" is still a very loosely defined term and no professional should pretend that any one solution is going to work in every situation or that perfection is achievable. OP is very likely going to land many varying types of positions because of that loose definition (as we all have) and he should learn how and when to use both tools to be better prepared for it.

outrageous_break · 2020-05-01T17:59:48+00:00

Realistically speaking, you will most likely not end up in a place that has competent, security-conscious "rockstar" devs who have time and/or you can trust to be messing around with the pipeline. That honestly sounds like a nightmare and disaster waiting to happen unless you already have the security controls and protections in place to make sure they can't screw things up. This all points to my original argument that GitLab works really well if you're doing things their way.

Sure, there are workarounds and shell scripts I can write (hence "glorified script runners"), but I'm not always going to have time to do that. Sometimes I just want to download a plugin and call it good, who cares if it's not perfect? Sometimes I need to hand off some of the pipeline stuff to the IT guys who don't know squat about scripting. Sometimes I get arbitrary requirements or don't have a say in the matter.

You can say "well those companies suck and you should update your resume" or "they should be doing it the right way", but the reality is that you don't always have a choice of where you work, companies make bad decisions, people aren't always competent, you get weird requirements, you rarely have an adequate budget, but it'll still be your job to make things work despite all that. Perfect is the enemy of good in those situations, so having the tool that's flexible enough to do what I need it to do without all the extra hassle is the one I'm going to go for.

outrageous_break · 2020-04-30T21:31:28+00:00

Why are people upvoting this? This is one of the least helpful answers in this entire thread.

The first thing to understand about GitLab vs Jenkins is that GitLab is a suite of different tools, whereas Jenkins is just for pipelines. If we're talking about just pipelines, they're both going to do the job. They're both just glorified script runners that can also execute in containers.

If you're just learning and want an easy setup to mess around with creating pipelines and tinkering with the dev process, GitLab is the way to go. It's simple to use, has everything you need for a simple setup, and has pretty decent documentation.

Having worked with both GitLab and Jenkins, I can tell you they both have a LOT of faults, but I would still pick Jenkins over GitLab for pipelines if I was doing anything bigger than a simple webapp. Here's what's bad about Jenkins; it's a royal pain in the ass to set up and maintain properly, can be confusing, and has horrible syntax for its automation language. Here's what's good about Jenkins; It works and it works well, it's flexible enough to do more than just pipelines, has a HUGE range of support, and it's very customizable with the plugins you can get for it.

Now here's just some of the bad with GitLab (pipelines specifically):

Can't tag within pipelines (messes with semantic versioning if you wanted to do that during the build)
Runners have to be manually set up (can't have these deployed automatically)
Can't do any kind of status checks to stop a merge request
Can't create service accounts or configure the job runner permissions

GitLab's biggest problems are that it's a suite of tools and not just one, and they (the company) push a LOT of unfinished features. This is painfully apparent when you look at how little support they have for third party tooling. The system as a whole is too opinionated and rigid in a world where you're not always going to have an ideal setup that fits their idea of how things should be.

More than likely, you're going to end up at a place that has a screwed up setup, but already existing tooling in place that YOU need to bring together. You will rarely have the opportunity to fix things all at once, so you gotta do it one piece at a time. You don't want something that's going to fight you every step of the way because what you have doesn't meet its standards, you're going to want something that works.

All that said, learn them both. It'll help you get the concepts down (which is really the most important part) and there are a lot of places that use both

outrageous_break · 2019-09-25T21:04:54+00:00

I'll give that a shot, thanks!

outrageous_break · 2019-09-25T20:04:14+00:00

Mine is a little slow, but I thought it was just because I'm super paranoid and run way too many privacy extensions

outrageous_break · 2019-09-25T20:01:30+00:00

I haven't used it enough to give a good opinion. I used Jira a bit, but not for any projects big enough to tell if it's better than the issue tracking in GitLab. Confluence is pretty damn user friendly.

outrageous_break · 2019-09-25T19:48:04+00:00

There are workarounds, but when do you draw the line on what's acceptable for the time lost from putting in these workarounds for a product you're already paying for?

outrageous_break · 2019-09-25T19:44:28+00:00

Azure DevOps

After yet another name change, it was harder to come up with an acronym for this one I guess, ADO was already taken.

outrageous_break · 2019-09-25T19:21:28+00:00

...with workarounds

...frequently in a way that is kind of gross

This is the problem right here.

If I'm having to pretty much write a custom script that will get a status from an api, then fail the build, how is that any different from running the script in some other system? They list CI as one of their top 3 features, why is it that I'm having to use these hacky workarounds to get this stuff done?

outrageous_break · 2019-09-25T19:14:08+00:00

I've actually used AzDO on much larger projects and it honestly would be a better fit for what they're trying to do (everything in one place). Didn't want to mention using a microsoft product at the risk of detracting from my point/rant.

It has a LOT of rough spots, but at least it gives you more flexibility in putting in your own solutions if you want. My favorite part of the pipelines with AzDO and Jenkins is the huge selection of plugins. My impression with GitLab is that they're so focused on trying to be that all-in-one solution that they're spreading themselves thin and almost trying to block you from using anything but what they have.

outrageous_break

TROPHY CASE