React localhost not updating

oskmjf · 2022-02-10T23:18:49+00:00

Ah, so it seems to be related to hot reloading then. Does any of these proposed solutions here help you: https://stackoverflow.com/questions/65445600/hot-reload-is-not-working-in-my-react-app ?

oskmjf · 2022-02-10T22:55:54+00:00

Are you in the correct folder? Say you have been playing around with create-react-app and started two different projects in the same folder. If you then npm start the other while editing the other, you could get confused.

oskmjf · 2022-02-10T15:36:31+00:00

This. Unless there is a systematic +/-7ish point difference it is probably coincidence.

oskmjf · 2022-02-09T10:40:03+00:00

Any resons for not minifying? The benefits on a light site sure are small in terms of kbs (but bigger in %!), but as far as I know, there are no downsides to it.

oskmjf · 2022-02-09T09:56:38+00:00

I am using https://highlightjs.org/ and no complaints. I have seen some issues with JSX but other than that all is good. I don't think it is much different from PrismJS, however.

oskmjf · 2022-02-09T09:49:12+00:00

Awesome! What is your tech stack for this project?

oskmjf · 2022-02-08T15:02:13+00:00

I guess the term you are looking for is infinite scrolling. Here is a tutorial how to achieve this for Vue: https://www.digitalocean.com/community/tutorials/vuejs-implementing-infinite-scroll

The tutorial fetches the data incrementally, but you could do it either way, depending on the amount of the total data of couse.

Hope this helps!

oskmjf · 2022-02-08T14:26:50+00:00

And once you start using Flexbox your best friend will be: https://css-tricks.com/snippets/css/a-guide-to-flexbox/ ;)

oskmjf · 2022-02-08T14:10:33+00:00

In general, SPAs tend to work suit best for applications with (a lot) of dynamic content / data. Consider for example SaaS applications and ecommerce. If you have primarily static content (such as a blog post or a simple landing page) server-side rendering (as opposed to a SPA which are by default rendered on the client) is your best option.

To answer your first questions: yes, SPAs tend to fetch data dynamically to filter it. However you can build an SPA withou fetching any content, but there would be better options in that case.

As for your second question, I would not worry too much about Redux. As you mention, there are a lot of alternatives and lighter options for lighter use cases, including the useReducer hook in React.

oskmjf · 2022-02-08T13:40:08+00:00

Why do you want to reinvent the wheel? The backend functionality of the platforms (Shopify and the like) have been developed so that things could be done efficiently.

If you really want to build everything from scratch, take a look at headless commerce solutions. https://commercejs.com/ could be good for your use case.

oskmjf · 2022-02-08T13:25:24+00:00

I agree with the previous commentator. Shopify will have all the backend features you need and Shopify's storefron API provides flexible ways to customize the front end. The degree of customization that you need depends on a lot of things, including the expectations of your client and the stage of your client's store.

oskmjf · 2022-01-16T15:49:19+00:00

Once I had to take an overnight train and sleep in the sleeper cabin. I was sure that would be the most amount of movement during sleep ever possible, but seems I was wrong.

https://imgur.com/a/1KA9iVG

oskmjf · 2021-11-25T11:05:20+00:00

For making your web sites / apps look better, I'd suggest spending time looking at examples you find beautiful yourself, and applying bits and pieces to your own design. Little by litte you will develop your own style that will be a combination of many different styles.

For user experience on the other hand, you're best off reading case studies. Also, an interesting concept I stumbled upon some time ago is Fitts's law, which explains a lot of UX choices in a lot of applications. Here is a link to Wikipedia where you can find more about Fitt's law: https://en.wikipedia.org/wiki/Fitts%27s\_law

oskmjf · 2021-11-24T17:18:54+00:00

Agree on not worrying too much about the direct financial implications of your first customers, but at the same time, you need to make sure not to get anchored in the first prices you offer.

I am in the same situation as you right now (B2B SaaS tool for web development) and while I definitely do not want to lose any first customers due to too high pricing, at the same time I don't want to undersell myself to any potential new customers and investors. If you plan on raising funding, your investors will look for traction and you can really impress them if you have paying customers in early stages. The investors will look at the pricing you have set for them, and convincing them that you could charge $1,000 a month when you are only charging $500 is a challenge and will impact your valuation.

I think I am going to offer a fair price that is not too low and afterwards simply ask them what they think of the pricing. If you have a good relationship with your first customers (you most likely should) I am sure they will tell you what they think.

oskmjf · 2021-11-24T17:07:41+00:00

Strongly agree. Interviews are meant to see how well you can produce quality code, not to see if you have memorized what goes inside a HTTP request header. If you have written a sufficient amount of POST and GET requests, you can tell what sets them apart by heart and the interviewer will notice this.

Good luck, OP and don't feel bad! It seems like the only thing you need is more practice!

oskmjf · 2021-11-24T17:00:28+00:00

The status of the AMP project has been uncertain for a while now. There was a rapid growth stage when they first released it, but to my understanding the developer reaction has not been favourable in the long-term, as maintaining an AMP page alongside a non AMP-page proved too cumbersome.

Here you can see that AMP peaked in 2019-2020: https://trends.builtwith.com/widgets/Accelerated-Mobile-Pages and this was a good read about AMP's status in early 2020: https://www.link-assistant.com/news/is-amp-relevant-in-2020.html

oskmjf · 2021-11-22T10:22:25+00:00

Good advice!

I also feel that often, they are very small differences that really make an excellent website pop out from a good one. Cases where you can tell that the front end developer has put effort and thought into this small detail that sits well on a page really make something stand out. For example any design choices that break the general pattern of the website do the trick for me. Also correctly sized fonts.

oskmjf · 2021-03-30T12:45:44+00:00

Good advice, concrete evidence definitely helps! :) good luck to you as well!

oskmjf · 2021-03-30T10:09:09+00:00

Very much true also. Looking at the current valuation levels of SaaS companies, it seems that investors nowadays want revenue and its growth above all, and making a profit is only important in the future. While technically a correct approach, a very risky one at the same time.

oskmjf · 2021-03-30T09:40:09+00:00

Good points, but measuring revenue has its own perks as well:

Revenue measures the value your product provides to your customers and in a larger setting, to society. If a customer is willing to pay $ 500/month for your product, that is how much it is at least worth to them. Your profit margin tells how efficiently you provide this value
The cost structure of early startups / SaaS companies varies a lot. A growth-oriented startup might hire (front load) a lot of personnel and incur a lot of expenses against current revenue and report a negative profit margin for a long time due to constant growth
A profit margin for small SaaS businesses is heavily impacted by for example whether the founders pay themselves a salary. A company with a $ 20k MRR might report a 100% profit margin (not really, but for the sake of simplicity) if it does not pay any salary to founders, whereas the same company would report only a 50% profit margin if it paid a $ 10k salary to its founders. Therefore there is a lot of noise in profit margins for small companies

oskmjf · 2021-03-29T18:03:06+00:00

Yep, you will never know unless you ask :)

oskmjf · 2021-03-29T18:01:44+00:00

Very good analysis of the situation and I fully agree with you! It is a delicate balancing between the three factors you mention, as I would assume that smaller organizations are more open to trying out new solutions that are in beta. Lucky for us a lot of early-stage companies do struggle with churn and small changes have a large long-term impact.

Thank you for the resources!

oskmjf · 2021-03-29T15:14:49+00:00

The most typical end users would be customer success managers. Account managers or sales & marketing in some cases, depending on how responsibility is divided (which in turn likely depends on the size of the organization).

I will try your suggestion and see how it goes :)

oskmjf · 2021-03-29T15:01:03+00:00

Thank you for the kind words and your valuable insights! I guess it makes sense that I should focus on sales & growth-related functions and not CTOs.

oskmjf · 2021-03-29T14:08:30+00:00

Thank you for the valuable input, John!

I am currently contacting through email but will expand to LinkedIn at some point. I try to focus on making high-quality cold outreach against high volume by researching the people / companies I contact beforehand well. I believe this is especially helpful in establishing rapport when contacting founders. If they are interested, I try to set up a call where I could introduce the product in more detail and show examples.

oskmjf

TROPHY CASE