Forem: Roger K.

Is it possible to blend DevOps w/ Full Stack Dev?

Roger K. — Sat, 05 Oct 2019 16:50:23 +0000

MY QUESTION
Are roles that blend backend/devops skills or do developers need to be
Full Stack or DevOps?

Background/POV
I'm currently a junior full stack web developer that has only worked in the industry for about a year. With a genuine personal interest in becoming more self-reliant I committed to doing all the AWS Associate certs before Jan 2020. Stretch goal is the Software DevOps Engineer Professional; we'll see if I can sneak a professional in by then. Either way I'll be happy.

Thank you in advance for any forthcoming comments and feedback.

How to progressively load 1000s of rows into a table

Roger K. — Sat, 20 Jul 2019 01:52:19 +0000

I'm using Vuejs (if that helps) and I'm requesting over 1000 rows from my database and wondering what's the best way to load that data?

I imagine there is a pattern, library or something that allows for a progressive loading (am I even using the right term) experience of some kind to the user.

Feedback: Looking to up my front-end skills

Roger K. — Thu, 24 Jan 2019 15:22:11 +0000

What can I do to improve my front end skills. I enjoy building the front end and working on interfaces too, but I need to dramatically improve my CSS skills and knowledge around UI/UX.

Do you believe online training programs would be wise and if so which ones would you recommend?

*I'm open to online bootcamps or Udemy stuff, so don't hold back based on price or learning style.

Do you know webpack?

Roger K. — Sat, 01 Dec 2018 05:11:51 +0000

Hi Gang,

I've been trying to learn Webpack for a while; the fact that I have been in forums for a while and asked for Webpack help and people always ask me if 'we can learn that together' is a testament that more people are struggling than those who know the topic.

I'd be really happy if someone could spend an hour this week with me to work through a couple setups that I imagine I'll use more than a few times.

The setup is relatively simple:

Express/Node
Pug/scss
Webpack to do the magic build process

I intend to use some variation of this stack repeatedly so learning how to use Webpack with those tools and having it explained to me; the why this and how come that would allow me to really grow my knowledge, because let's be honest the hardest thing is getting that first cohesive effort together and then growing outwards from there.

IndexedDB, something to rely upon?

Roger K. — Mon, 17 Sep 2018 18:46:02 +0000

Could I build a Progressive Web App using IndexedDB as my sole form of storage?

My supposition is to build a suite of apps that work together and are local; calendar, tasks, contacts, etc that run exclusively inside the browsers domain. They don't need to install an 'app', they don't need a web service to function. Just go toa webpage, click add to desktop an like Dev.to and voila it works.

Can this be done? Why hasn't this become common? What are the risk factors?

More specifically, I'm clearly going to rely on IndexedDB, right? Is that bad/good? Why?

I'm sure there are reasons for why this hasn't happened, but if I could I'd like to aggregate all the feedback into this one article for myself and others who may be considering the same thing.

Your assistance is greatly appreciated!!

Is using Docker for a small OSS project a wise decision?

Roger K. — Fri, 14 Sep 2018 16:44:00 +0000

Project overview

Currently I'm trying to assist an open source project and I suggested that since we are spending lots of time trouble shooting configuration settings over multiple platforms, versions, etc that we consider using a Docker container with our stack preconfigured, so the new contributor (I believe) only needs to spin up that container, clone the repo and start coding.

Is Docker the right tool? Will it create more overhead than we realize?

As someone who has only read about Docker until now; laptop wouldn't support it until I got my new one this week - woohoo - and since it's something I'm excited to try I suggested it. It was accepted as a possible way forward and now I'm stuck with my biggest fear; did I pitch something that isn't a good solution.

If this isn't the right tool....

... then do we stick with package.json to run the full set up or is there an alternative? I'm fine with sticking it out with package.json, but I was just hoping to simplify. It's important to understand this OSS project is supported mostly by newer devs, so if it's not simplifying for them then it's a no go for us.

It needs to be both the right tool or improvement for the job and make on-boarding of new contributors more *simplistic than now using package.json

What are your thoughts?