Jump to content

Jack

Moderators
  • Content count

    3,283
  • Joined

  • Last visited

About Jack

  • Rank
    🐐
  • Birthday 08/23/1991

Users Experience

  • Experience
    Advanced
  • Area of Expertise
    Web Developer

Profile Information

  • Gender
    Male
  • Location
    Jersey Channel Islands
  1. Visual Studio Code

    HTTPS is password based, and gets a bit annoying because it will prompt you to enter your git credentials more often than an SSH key. Once you have an SSH key added it's much easier to continually use, you don't really have to do anything from one project to another. They can be easily revoked and setup again without having to update the credentials across all of your projects. SSH keys are also more secure, a password can be cracked, or if you re-use passwords (you shouldn't) it could unknowingly become compromised. SSH keys can't be cracked as far as I'm aware. Another step I'd recommend setting up is 2-factor auth on your accounts, which will prevent people from logging in without a code sent via an app or SMS. I'd recommend doing this on as many services as possible because it will give you an extra layer of protection. The last thing you want is your email comprised, because things start getting real difficult when that happens.
  2. New Forum Logo - the winners

    Yay, second place isn't bad. Although I know everyone will miss my first logo. In case people are curious, because I entered, I didn't have any vote or say in the results, even as a moderator. It's only fair that way.
  3. can't get gulp to work

    I've never had permission errors with any node module, but it does happen. Try running: npm uninstall gulp-sass and adding it back in using sudo npm install gulp-sass --save-dev You shouldn't really have to install with sudo but it may fix this issue.
  4. can't get gulp to work

    Did you copy this from an existing Gulpfile? The syntax changed from V3 to V4 and that could cause the error above to throw. Could you post your package.json file?
  5. Caching for Google Maps?

    As far as I'm aware, you won't be able to cache third-party scripts like this, because the files don't live on your server. Generally I recommend taking PageSpeed Insights with a pinch of salt, it simply looks for a set of rules and detects whether they pass or not. Most of the time the service will even complain about things out of your control like version numbers on files, even if they are Google's own product set by them.
  6. Prefetching

    They need to go inside your <head> before any of the third-parties are called. They basically resolve the DNS ahead of time, so that you don't have to wait for the DNS to resolve when you get to the external resource. This generally means the script is ready to be fetched once the browser gets to it, rather than having to sit there waiting. It still has to fetch the data, but it has already verified the DNS at this point and can get straight to doing that. If you have 5 third-party scripts, 5 DNS lookups have to occur, and rendering will be blocked in the meantime. You can't be certain of how long this process will take either. This tag won't control the loading of assets in the case you've mentioning above, it's not a queueing system, it's just a way to tell the browser what to expect before it gets to it.
  7. That does make sense, I wasn't aware that browsers won't action HTTP requests unless the rule for the media query is met. I think it would slow me down a lot building mobile-first now, especially when our designers at work are really good at knowing web layout, and we use build tools that drastically reduce the amount of CSS sent down the wire anyway. Maybe I'll give it a go, who knows.
  8. I agree, this is what the original book is about, but it has been skewed a lot. The book doesn't mention how you should build a site by reversing your media queries, Luke Wroblewski is a UX designer foremost, and it's heavily about how you should be designing and collaborating on the best mobile first approach, not designing a UI element for example that can only work on desktop, like a complex table. It's also about content prioritisation, if something exists on desktop and not mobile, you should consider removing it entirely, or redesigning it, rather than the display: none approach that was so common back then. It's 100% a UX book. I'm not sure how true this is. Mobile-first shouldn't even be concerned with the structure of your CSS in reality. If you have a bad design, no build style or amount of development work is going to save it, mobile-first needs to be at the design phase not development. I have never built a site or application using the mobile first approach and it always ends up exactly the same as if I would have. The original book that the mobile-first term came from doesn't mention this approach of development anywhere. From what I understand, wrapping an element in a media query makes no difference to the amount of CSS that's downloaded. If media queries dynamically download CSS only for that size, then this is the first I've heard of it. I always assumed the entire bundle gets requested unless you're doing some kind of server-side detection.
  9. Wrappers and Containers

    In that case it's just a way to group things, some people call them wrapping elements, some containing elements. All they are is something like <div class="container"></div>.
  10. dotvoice

    Overall it looks really nice, but the feel isn't very personal. It mentions on there that you're an agency, but there's nothing really on there content-wise about who you are, if you have a team, a physical office etc. I would definitely consider adding some work to the homepage too. I personally think these are two great examples of getting that agency feel across https://sidigital.co/about https://madebyshape.co.uk. Both have a reassuring aspect to them, that they are capable of doing the job well, and have experience. Lastly, the studio part is a bit confusing, is it a product, or a services page? I was kind of expecting to see photos of your offices and team here.
  11. Go on Teo, midnight is plenty of time. I designed mine in an hour after all
  12. Torn between UNI CHOICES!

    I don't think you're asking in the right place. I'd be surprised if anyone one here has personal experience with those courses, certainly not any outside of the UK. If you're looking at a design or UX course it's unlikely you'll do any programming. Some digital media courses might, but it's going to be incredibly basic in comparison to something like computer science.
  13. General JavaScript

    I was going to create a repo on Github with some examples in to test, but I've been hungover for like 2 days, because I'm getting old now. I haven't been too motivated because of it.
  14. General JavaScript

    GraphQL is an awesome concept, I think you'll prefer it over REST. I'm working on a todo REST API at the moment actually, for practice, and have been testing my Express endpoints using Supertest (http://willi.am/blog/2014/07/28/test-your-api-with-supertest/), but I'll likely refactor to Jest if Jest can do that sort of thing. Having multiple testing libraries seems a bit counter productive to me. The code you wrote above makes a lot of sense, especially finding a mock for localstorage. If you didn't have that package, would it be fair to create a similar data structure to localstorage and test against that? It's basically an object, so could you just check that you're passing values into an object, and then removing them? It's not 100% accurate but it's close, and that package must be doing something similar. On the subject of mocks, since they are mentioned a lot on here. What are your thoughts about the whole 'mocking is fragile' or 'don't use mocks' debate that you see in TDD? It seems like you need to if you're asserting an API or Database. Eric Elliot goes on about this a lot, but I'm not sure I value his opinion on some stuff.
  15. Picking up old projects and question about bugs

    If it's a personal app then your technology choice won't make too much difference, although I don't think I'd go for any of the C languages as they tend to be very low-level. Is there a language that you would like to start learning more? Side projects are often a great way to do that.
×