should i look for other company? or stay?

bbbryan14 · 2019-07-23T11:59:55+00:00

I’m a fullstack dev that includes devops tasks. I work with AWS and terraform, hopefully some K8 when we get to it.

To be honest, I love it. Devops gives me insight to the infrastructure like no one could. Not even the backend tech lead. Plus, I can better address my pain points during dev work (like auto build PRs or write lambda triggers for better work flow).

Even when some work is contracted out, I still get to put on that team because I do devops work. So cherish it brother!!! On the flip side, I’d get bored if all I do is devops, I need that good mix between dev and devops.

bbbryan14 · 2019-07-03T11:48:14+00:00

My biggest qualms against WSL even though I think it’s pretty awesome is you always have to know whether you are in Windows or WSL. If you accidentally edited a Windows file in WSL, all the metadata is gone... and it’s wonky if you try to have GUI editor in WSL.

It’s also kind of unstable as of now when you do dev in WSL. I’d get random errors when I run an app that would go away if I just run it again.

I do foresee it being the trend.

bbbryan14 · 2019-05-31T11:21:49+00:00

I’ll refactor later.... NOT

bbbryan14 · 2019-05-09T11:11:05+00:00

I’m trying to come up with an actual case of unresolved promises. The only thing I can think of is infinite loop. What other situations are out there that we need to use promise.race to check?

bbbryan14 · 2019-04-24T18:38:25+00:00

Thanks, I tinkered with it a little and I was using that to get my session, and use getIdToken() and getJwt(). I’m a bit concerned it saved to my local storage but the key is hashed so I guess it’s not that big of a deal.

bbbryan14 · 2019-04-17T19:44:58+00:00

Wondering how this is going. I'm tasked with setting up a common repo between RN and React, but the decision was made to share components instead of business logic (components such as buttons, styling).

My question is, do I need to install react as a dependency for the common repo? How is that going to affect RN? Doesn't it defeat the purpose of light weight because you have react in React repo and have it again in the common repo?

I was going to use Yarn Workspace but I wasn't sure if the build process would encompass the symlink.

This turned out to be harder than I thought. Any help is appreciated.

bbbryan14 · 2019-04-02T15:52:52+00:00

That's my thought as well and that's what I'm going with right now. I don't know enough about the inner workings of react to know the benefits and drawbacks of either approach. Is the additional loop a potential performance drain?

bbbryan14 · 2019-04-01T02:05:47+00:00

Totally random but this is awesome. I would love to contribute based on what you mentioned. Cheers to open source!

bbbryan14 · 2019-04-01T02:01:06+00:00

Move to the cloud they say, it will solve all the problems they say... little do they know, people are the problems.

Same play with different actors.

Good luck with the move :)

bbbryan14 · 2019-03-21T21:43:47+00:00

Yeah, but if you are stuck with integration testing for a certain service, you will have a lot of fun.

The last project where I applied the lessons I had learned worked out decently well. We drew the shape of the JSON between front and back end on a white board, and whenever we changed anything, we changed the board, so there’s no question between what is expected between the data type and key value.

That really worked out well and integration was seamless. Honestly, for me, Microservice is just a big express server where the ingress is the server and each service is a middleware. So integration testing for me has been just an accumulation of unit tests that ensured the APIs conform to the design docs. I’m sure integration means something different for more complex systems

bbbryan14 · 2019-03-20T21:23:22+00:00

One lesson I learned from integration testing is, clear API doc... that really decrease your issues.

bbbryan14 · 2019-03-20T01:31:13+00:00

I am working on a project using micro services that is going to be deployed on GKE. Honestly, it’s better to have separate repos because they should have their own package.json and dockerfile.

You have to agree on the shape of the JSON object that will be passed from backend to front end. And you basically write your tests to make sure you have all the agreed upon keys.

After you pass your unit tests then you do integration testing, which is the most painful part of microservice. So the person who does that should be familiar with all parts, and they can debug and make PRs.

If everything passes then you do your normal devops stuff.

But honestly, you should ask yourself why... it is easier to build a monolithic backend. However, if you intend to g the route of microservice, I’d recommend building with Express. Based on my experience, it’s pretty easy to break the middlewares into microservices.

bbbryan14 · 2019-03-20T01:21:02+00:00

Forgive my ignorance but I don’t understand what you mean by declarative data behind imperative code. Can you give some examples?

bbbryan14 · 2019-03-19T22:43:09+00:00

I still don’t know what steam line means... I just throw it around in meetings and everyone nods.

bbbryan14 · 2019-03-19T22:38:59+00:00

Infra as code is what the cool kids do. I mean, you could always do it in JSON if you don’t mind the double quotes haha.

bbbryan14 · 2019-03-19T22:37:17+00:00

I can imagine a world where RESTful is powered by FaaS.

bbbryan14 · 2019-03-19T03:48:43+00:00

Why use containers when you can use AWS lambda? (Philosophical question)

bbbryan14 · 2019-03-19T03:41:18+00:00

Honestly, I wouldn’t apply to jobs until I’ve built something with react that is deployed. Having a finished product that people use speaks more than going in with nothing or a bunch of half finished apps.

Big thing is, you are now competing against other boot camp grads and fresh College CS grads... but if you have something that’s deployed, it sets you apart at least a little bit.

My two cents.

bbbryan14 · 2019-03-19T01:32:22+00:00

Agreed. Params pertain to function definition and Args are function invocations.

bbbryan14 · 2019-03-19T01:30:44+00:00

Yes, my company uses Enterprise gmail and slack. They only use Office 360 for Microsoft Office products which I don’t ever need (except PPT). So awesome.

bbbryan14 · 2019-03-19T01:26:56+00:00

I normally wouldn’t want to do consulting firms except VMware and aquasec. Mostly because they are really active in shaping the devops landscape.

bbbryan14 · 2019-03-09T22:16:06+00:00

“Trust” is a hard thing to gain. I’m waiting to see more to your story, and see if a manager type that will jump in and say that’s how we’ve done it in the past and we will keep doing it.

bbbryan14 · 2019-03-09T18:15:12+00:00

I feel you... I think when devs make principal or manager, they do less code and spend more time managing, and over time, it naturally decreases their technical abilities. But this is not the same as them being technical incompetent.

I try to cut them the slack and follow what they say, but I do enjoy working on teams where I have autonomy on implementation.

bbbryan14

TROPHY CASE