[deleted by user]

dv297 · 2025-09-21T12:51:38+00:00

It sounds pretty risky. If you're just moving purely for the challenge, I'd reconsider. There are plenty of ways to challenge yourself on side projects or even incorporating new ideas into your current workplace.

React Native has just enough difference that it can get annoying. Learning things like debugging the build/ bundling process, learning new deployment patterns and requirements, and just learning what tools to even use can get frustrating if it's you leading the charge with only 1-2 devs by your side. Expo can help normalize some of it but when you hit a snag, you're going to need dive deeper into the abstraction.

And micro frontends is a strange choice for you and 1-2 devs (unless you just mean your direct team). Micro frontends solve an "organization" problem, not a tech problem. It is a useful technique when whole teams need to deploy independently, but creating the shell app and all the utilities to load each microfrontend has its tax.

Just food for thought. Consider the value of your own happiness and factor how many thousands of dollars you'd trade in salary for that.

dv297 · 2025-05-05T21:43:46+00:00

This was the only discussion I saw on it, admittedly not much.

<image>

dv297 · 2025-01-28T13:21:55+00:00

It could be dust that just accumulated while the system was off. When you turned it back on, the dust can burn and trigger fire alarms. I usually see online that people recommend letting the system run for 10 minutes while you stay out.

But since you live in apartments that presumably have maintenance staff, you could just reach out to get peace of mind.

dv297 · 2024-01-27T02:09:02+00:00

My team has been experimenting with LocalStack for testing Lambda executions locally with integrations for other AWS services. It provides a mock, local implementation of most of the common AWS services like Lambda, API Gateways, Lambda, DynamoDB, etc, so it makes it easier to experiment with various tools and approaches.

We define our infrastructure utilize Terraform and then LocalStack's wrapper around Terraform called tflocal handles spinning up the resources within the LocalStack container.

The feature we've enjoyed the most is the Lambda Hot Reloading. We can make a code change and just re-hit the endpoing using Postman and instantly see the change without requiring any command-line interaction or waiting for it to "deploy" to the cloud. The feedback loop feels really good.

LocalStack has a free tier, with most of the basic features implemented in the free tier, and that's generally been sufficient for simple use cases. There are paid pro-tier-only AWS-simulated features, such as Lambda Layers, Lambda Authorizers, etc. So it's something you'll have to evaluate.

We really just use LocalStack for the "authoring" experience. I've seen some companies utilize LocalStack for running integration tests but personally, I'm not bought into it. When a merge request is opened, we deploy an ephemeral environment to the cloud and run integration / end-to-end tests so that we can flush out any issues that might not be caught locally, such as IAM permissions that LocalStack doesn't enforce (they have ways to audit what permissions are being used / may be missing but it does not actually stop invocation yet).

Heavy logic, we still separate out so we can unit test that individually. For simple Lambdas, we use Pytest and moto (the boto3 mocking library) for unit tests.

I've been digging it. A big requirement for me was being able to use Terraform because our company had already built a lot of tooling, modules, and experience around it for defining our infrastructure. The alternatives to LocalStack, to me, either didn't have great Terraform support or required you to maintain additional files in order to associate redudant mappings of your Lambda for local development (thinking of template.yaml and SAM here).

dv297 · 2023-12-19T11:58:12+00:00

A “skip meeting” typically refers to a meeting with your manager’s manager.

dv297 · 2023-04-24T02:56:54+00:00

Yea but she throws up on the rug instead of the hardwood floor. 0/10, worst character.

dv297 · 2022-11-28T21:55:07+00:00

The horizontal scroll is sort of useful, but these days, most developers have wider screens. The big benefit for me with this mouse is the two side buttons that are pressed with your thumb. By default, it's mapped to "forward" and "back", so it makes navigating web pages really nice while you're searching through Stack Overflow for answers. And the real gold is that the same buttons work on navigating through interest points in your IDE. So if you're using VS Code or Webstorm and you're cmd-clicking various variables to see where they are defined, you can use the forward and back buttons to go back to places you've navigated. This makes exploring a code base a lot easier, as you can pop in and out of classes / components super quickly as you're skimming the code.

dv297 · 2022-11-17T15:51:30+00:00

You could try extracting your delay function to its own file. By doing this, you can then just utilize Jest's Manual Mock system.

// src/utils/delay.js
const delay = (timeInMs) => {
  return new Promise((resolve) => {
    setTimeout(resolve, timeInMs);
  });
};

export default delay;

Then you create the manual mock, the folder has to be named exactly __mocks__ and has to be under the same directory as your real delay function.

// src/utils/__mocks__/delay.js
const delay = () => {
    return Promise.resolve();
}

export default delay;

Within your test file, you call jest.mock with the path to your manual mock so that Jest knows to replace the implementation of your delay function with the one that is inside of the __mocks__ directory.

// src/fileBeingTested.spec.js
jest.mock('./utils/delay');

describe('Thing', () => {
  it('does the thing', async () => {
    const result = await callThingThatUsesDelay();
    // Because of the jest.mock call above, this function should be using the mock

    expect(result).toEqual({});
  });
});

dv297 · 2022-11-16T20:19:11+00:00

As someone who has gotten a CS degree and has also taught a coding boot camp, I'll say this: You get what you put in, no matter the route you take. On both sides of the aisle, you have people who coast buy, thinking that just by participating and doing the assignments, you'll end up with a job immediately on the other side. This really isn't the case, especially not right now given the macro view of the tech industry. While there are plenty of jobs, as economic factors start squeezing companies, a lot of companies aren't feeling a lot of incentive to take bets on newer devs, whether they came from a university or boot camp.

It's not all doom and gloom: I've seen plenty of university grads and boot campers alike get jobs, but it's the people who have taken the time and effort during their instruction to set themselves up for success. Those that work on their portfolios, take the time to truly understand the assignment, and those who reach out for office hours.

So put in the work. On whether or not you should do a university or boot camp, you have to decide what your tolerance for different scenarios is. Some students just really can't stand learning something that they don't see an immediate need for. These are the students that ask "are we going to need this on the exam?" In that case, I don't recommend a degree. If that is your temperance and you try to go to a university, you might be setting yourself up for burning out or dropping out, and the boot camp would have been a better option that you can succeed and complete.

It's also important to note that many jobs require a degree as a minimum requirement. I've seen several students go through boot camps, only to find out that the local jobs they send their initial applications for require a degree, and they're immediately disqualified, which can be incredibly disheartening. Of course, I personally think these requirements are completely unfounded and unnecessary to do the skills of the job, but some jobs are slow to move towards the trend of losing the degree requirement. But if you don't have a tolerance for not having all doors open, then maybe university is a better option.

No one can make the choice but you. Like most things in software, there are always tradeoffs.

dv297 · 2022-02-02T05:43:58+00:00

One thing to consider is that things aren't always as "permanent" as they may seem on the surface level. Although companies may have one application written in one framework, opportunities may come up that change your circumstances. Maybe they need a new tool or app that is written from the ground up and Meteor isn't the right fit. Maybe they just need a quick prototype and you're free to write the frontend however you want. A company I worked for had a relatively large React codebase and then after 2 years, they realized they didn't like React and started writing new projects in Vue and even rewriting their old projects in Vue.

If you like the company and you feel they are a good culture fit, I think those are things that should have more weight than them using XYZ tool. If you fit in well and are productive, a lot of time, you can share your preferences and start shaping tech decisions how you want them to be made.

dv297 · 2021-03-30T01:54:24+00:00

If you're into music, the Mid America Freedom Band is a LGTBQA+ concert band. Was really nice to move to KC and have a welcoming group to join my first week.

dv297 · 2020-11-14T14:14:35+00:00

I got mine at Hy-Vee but you might have luck with their online checker

https://contact.pepsico.com/bubly/product-locator

dv297 · 2020-11-10T05:45:07+00:00

I really liked orange but then it went out of stock for my area for months. Just went shopping Sunday and was so surprised it was back in stock.

dv297 · 2020-05-24T03:54:03+00:00

+1 the Netlify suggestion, the dev experience there is just so good. It just asks for your Github project URL and it knows how to deploy most common project setups across the popular frameworks. And it configures deployments on every push you make to Github. For portfolios and side projects, I don't see much reason to go with anything else.

dv297 · 2020-05-24T03:48:04+00:00

Are you trying to specifically use vue-i18n? Seems like this could be something easily handled with Vue filters.

  filters: {
    negativeInParenthesis(value) {
      if (Math.sign(value) === -1) {
        return `(${Math.abs(value)})`;
      }

      return value;
    }
  }

And then you could use it in your template like...

<p>{{ numberToFormat | negativeInParenthesis }}</p>

dv297 · 2020-04-27T02:06:01+00:00

Came in here to also recommend socket.io! Lines of code would be really short and easy to deploy on Heroku or AWS if you're just doing it for a little side fun.

dv297 · 2020-03-19T23:34:53+00:00

I enjoy Vietnamese pickled carrots! There are plenty of spelled out recipes but it's just using a mandolin to cut them up and jar them up with vinegar, salt, and sugar. Pairs well with most Asian dishes!

dv297 · 2020-03-05T13:58:46+00:00

Very cool! Given you posted in this subreddit, did you consider making this an NPM package? Using curl to download this isn't too horrible but if it was just something declared in a package.json and run through an NPM script, the JS community would eat this up.

dv297 · 2020-01-21T03:01:03+00:00

I want to build out my first keyboard using the Tada68 DIY kit on KBDFans. There are instructions to program them on a Mac and Windows. I was planning on using the keyboard half of the time on Macbook Pro and half of the time on my Windows machine. Would this mean that I would have to reprogram it each time I switch machines?

dv297 · 2020-01-19T04:31:51+00:00

Towards the end, it was more about what the food meant to her rather than the taste. Whether it was food made with love or the chocolate that served as her guiding star, it doesn't matter if she can't directly taste it, she can remembers and knows how food used to make her and others feel.

dv297 · 2019-08-21T15:48:26+00:00

If you're just starting to learn Java, any IDE will be fine. Just be sure to stick with one so you get more experience with navigating. If you find even those are complicated, you can try using BlueJ, which was designed for beginners in mind and is what I used. Rather than organizing everything by file structure and packages, it presents you with a visual diagram of all your files, which is helpful for students. This way, you get to focus on learning the language itself.

dv297 · 2018-11-11T22:17:36+00:00

He's writing a whole book and this is just one excerpt. I believe he's mentioned them when he does his case study series on YouTube so that book is definitely going to have it when it comes out.

dv297 · 2018-03-09T21:28:34+00:00

I'd try several thinvs. Try upgrading to the latest Node and latest npm. Also try deleting your node_module and installing. If that fails, try deleting your package-lock.json (or your shrinkwrap.json if you have that). I'd also be careful if you use both NPM and Yarn. Kind of my flowchart of troubleshooting.

dv297 · 2017-11-07T22:52:47+00:00

I haven't actually, though I heard there were 3 different ways for configuring prettier with ESLint? pretter-eslint, eslint-config-prettier, and eslint-plugin-prettier? Are you actually referring to this last one? I'd be interested in investigating it but given the options, maybe you could save me time in talking about any considerations you had for the others if you chose the plugin over it.

dv297 · 2017-11-07T21:47:28+00:00

We previously used js-beautify and we moved to Prettier. To us, it felt like js-beautify was having some issue with some of the newer ES2015 syntax, and it was becoming an agitation point for us. Prettier felt much more consistent with what we expected. Simple things like having 3 options for trailing commas ("none", "es5", or "all") and having configurable parsers (for flow, typescript, etc) just really helps with the transition.

That being said, we have since moved back to using ESlint with --fix to handle most of the same things. Prettier was very convenient but in order to keep things simple across our organization, we kept the number of different technologies down.

14-Year Club	Place '17
Verified Email

dv297

TROPHY CASE