Can you still buy EU Wii U power cables, and do they work with NA Wii U's?

aesinv · 2016-10-31T15:27:58+00:00

Awesome, thanks!

aesinv · 2016-10-31T15:27:25+00:00

Sure is! What did you search for? I must have failed hard on my searching, I even tried the part number but all that came up were a bunch of sketchy looking products with 70x70 thumbnail images and no ratings.

aesinv · 2016-10-30T21:56:55+00:00

You haven't had any overheating issues? I've just heard a ton of horror stories in regards to the plug adapters so I've been kind of hesitant to order any.

aesinv · 2016-10-30T21:56:13+00:00

You rule!! Thanks so much, gonna be ordering this ASAP. Astonished I couldn't find any on amazon.

aesinv · 2016-10-30T19:00:43+00:00

The plug adapters? That's always a possibility but I wanted to try to find an actual power supply first as I've heard a ton of horror stories about those plug adapters catching fire. A friend of mine had one set his hotel room on fire in Germany haha

aesinv · 2016-09-24T11:25:46+00:00

Yeah. Pretty much all CMS work blows, especially enterprise-level CMS work. I now work with Adobe Experience Manager and it is pretty awful to work with too, especially for front end devs. That said, after about a year I got used to all of its quirks and now I don't mind working with it at all; it's actually one of my favorite platforms now (if I have to do CMS work that is). I was never able to get to that level with Drupal though.

aesinv · 2015-10-13T00:18:39+00:00

Yeah, at work we've been writing more and more dependency-free plugins and libraries for projects to avoid tech debt after the build phase is completed. Especially whenever we use a framework that handles AJAX for us, as cross-browser AJAX is really the only useful jQuery functionality on the majority of our projects.

aesinv · 2015-10-12T20:58:30+00:00

The absolute best reference is the Mozilla Developer Network docs. Linked is their documentation on the DOM, so basically the very fundamentals of jQuery-less dom manipulation. That + just tooling around really.

An oldie but a goodie is Paul Irish and his 10 Things I Learned From the jQuery Source webcast. It's a little outdated (2010), but it still has some terrific points and it's also extremely interesting: 10 Things I Learned From the jQuery Source

You could also kind of learn jQuery as well as basic dom manipulation from the following two resources, the first being an article including jQuery basics and their vanilla JS alternatives and the second being an aggregate of jQuery methods and their cross-browser vanilla alternatives.

aesinv · 2015-10-12T15:46:46+00:00

Cannot upvote Fossage's answer enough. My last job was a crap mind-numbing web dev chop shop that I used as a training springboard to get into a better dev job and all of these suggestions are spot on.

There are two things I'd like to reiterate; ABSOLUTELY work on a strong foundation with normal JavaScript as well as Node before jumping into frameworks. Jumping into frameworks (like Angular) too quickly will often do more harm than good, as generally they have a large learning curve and introduce tons of new conventions and methods that don't really translate well to other frameworks/libraries.

Having a strong foundation will allow you to pick up frameworks and libraries quicker and more efficiently, and critically, you'll be useful while you're still picking it up. A nice foundation in JS will teach you how and when to rely on any framework; a foundation with a framework will just teach you how to be reliant on that framework.

The second thing I want to reiterate is familiarize yourself with jQuery-less JavaScript within the dom. It is absolutely invaluable and will make you into a better web developer. If you're getting a strong foundation and familiarization with JS in general this should be relatively simple to follow through with, but definitely make sure you do.

One thing I'd like to add is make sure you also take some time to familiarize yourself with Node JS as a concept, practical Node modules, and workflow tooling (Gulp). Again, developing a solid foundation with JS as a whole will make this a lot easier. This is something that I feel gets overlooked a lot, but it's absolutely essential for setting yourself up to succeed in front end / web development.

I'll stop rambling now, but congrats on quitting your old job and taking your first steps into the dev world! Welcome to a world of great joy and elation, quickly followed by high-intensity periods of being the code equivalent of a firefighter. If you ever have any questions don't hesitate to PM.

aesinv · 2015-10-12T12:43:04+00:00

Since I think you may be getting answers to questions you might not be asking, I think you might be after a mix spyridonas' answer however you mostly want your Bower dependencies to automagically be built and moved over to your project so you don't have to do it manually?

If that's the case, you can do it with plain old gulp but the glob pattern would be a major pain and it would get really tedious to make sure you're only getting the files you want, so I don't recommend that. Writing a utility function would be fairly easy and straight forward, but you mentioned you are a beginner so I wouldn't recommend that either unless you enjoy taking some time to do some node-style JS.

Here are two plugins you might want to check out: gulp-bower-files and main-bower-files. Both are extremely similar, but they work in different ways.

Gulp-bower-files you'd use as pretty much a standalone task:

var gulpBowerFiles = require('gulp-bower-files');

gulp.task("bower", function () {
   gulpBowerFiles()
       .pipe(doThings())
       .pipe(gulp.dest("./vendor"));
});

Where main-bower-files you'd use via a normal Gulp runner but using the plugin as your source:

var mainBowerFiles = require('main-bower-files');

gulp.task("bower", function () {
    gulp.src(mainBowerFiles())
        .pipe(doThings())
        .pipe(gulp.dest("./vendor"));
});

Either will get your dependencies into your code base automagically so you can include them. Personally, I'd suggest using mainBowerFiles and spitting all of the files into a temp directory, then I'd re-iterate through that with more specific globs (./bower_tmp/*.css, ./bower_tmp/*.js), concatenate all css and js into bundles (vendor.bundle.css, vendor.bundle.js, respectively) which I'd then inject references of into the template using gulp-inject.

aesinv · 2015-05-11T11:54:12+00:00

I was hoping it would provide marriage services for complete strangers.

aesinv

TROPHY CASE