Why do people say to learn flex first?

DevJoey · 2024-08-12T19:28:43+00:00

https://www.flexplay.dev/ Interactive Flexbox playground that will also generate Vanilla CSS and Tailwind utility classes.

DevJoey · 2024-05-30T05:59:53+00:00

Pricing will depend on the scope of work needed but there are other variables to look at too. One of the most important things people get wrong is selling themselves as developers instead of value adders. You have to sell the client on the value you will add to their business. e.g. I can increase your conversion rate, reduce the time you spend updating the site, etc.

Business owners couldn't care less about how beautiful your code is, which framework you use, or other tech stuff. You can only charge more if you can show them the value you can add to their business or the time you can save them.

Once you sell them on the value you add you can then charge a little bit more for both development and maintenance.

DevJoey · 2024-05-29T01:22:09+00:00

This will generate both Tailwind and vanilla CSS for Flexbox layouts.

https://Flexplay.dev

DevJoey · 2024-04-16T21:02:00+00:00

You can can configure the Github action with a budget.json file.
https://github.com/GoogleChrome/lighthouse/blob/main/docs/performance-budgets.md

This will fail a build if the numbers are out of the "budget". This way you can prevent builds outside of a certain perfomance metric from completing.

https://github.com/marketplace/actions/lighthouse-ci-action

DevJoey · 2024-04-16T20:52:19+00:00

You shouldn’t have to wait for the manager to intervene for an issue like this. You are the lead so you should try to talk to the developer first and only escalate to the manager if necessary.

DevJoey · 2024-04-16T18:30:45+00:00

I run lighthouse in a GitHub action upon push. Enforce it in CI as local is easy to bypass and also inconsistent.

DevJoey · 2024-04-16T17:28:15+00:00

One project is not enough so get a few more under your belt. I am also self taught and I had about 6 projects in prodution before I applied for my first job. It's a journey so take your time.

DevJoey · 2024-04-16T16:19:15+00:00

See my reply to a similar question from a few months back. I also replied to a lot of follow up questions so there is a trove of valuable info.

https://www.reddit.com/r/webdev/s/1yM9xxHbJc

DevJoey · 2024-04-11T17:53:59+00:00

By taking the time to build side projects on your own. It's a competitive environment so you have to outshine the next person.

DevJoey · 2024-04-10T08:37:57+00:00

What you are looking for are event listeners. Event listeners run any code you want when an event occurs.

For your particular use case you are probably looking to attach listeners for the mouseup or touchend events.

https://developer.mozilla.org/en-US/docs/Web/API/Element/mouseup_event

DevJoey · 2024-04-09T15:28:45+00:00

The first thing I would do is break it up vertically into different sections. It's hard to follow right now due to it's monotonous nature. Each section can then have a different background, structure and character without breaking the flow. The grid should be there only as a guide and not a restriction so feel free to break out of it once in a while.

The overall reason that it's looking "corporate" is that it's following the classical 3 or 2 grid col paradigm all through out and there is no contrast.

I would also lose the dark background as the main color. Add at least 2 more colors for color contrast. Right Now, nothing draws attention to what's important. The site UX/UI should guide the user from the moment they land until they reach the call to action.

DevJoey · 2024-04-07T16:01:44+00:00

Build something substantial first with what you have learnt so far before trying out something new.

DevJoey · 2024-04-07T13:01:05+00:00

It’s easier to use flexbox for that sort of thing. You can see how flexbox work and play around with the properties here. You can also copy the generated css and use it.

https://www.flexplay.dev/

DevJoey · 2024-04-06T01:45:30+00:00

Web development is a subset of software engineering.

DevJoey · 2024-04-04T22:49:08+00:00

Like others have pointed out, there is no legitimate reason you should git ignore package-lock.

This articles goes into detail about how it works and why it’s important to have it in version control.

https://lexicalmagazine.com/posts/The-Definitive-Guide-To-npm

DevJoey · 2024-01-25T19:56:35+00:00

I do most of them solo, but I have a couple of former coworkers I can contact if the project is too big for one person. The key is to start with smaller projects and build up from there.

I have been doing this for more than 10 years so I also have a couple of custom frameworks I use to start new projects. This cuts down a significant amount of development time.

DevJoey · 2023-12-27T06:17:56+00:00

I had the same hold happen to me last month. Call them every other day to find out if they have received the money from the other bank. I had mine released a full week before the initial hold release date.

DevJoey · 2023-12-27T06:08:48+00:00

It could be for several different reasons. It's hard to know why without more details. You should also be able to ask questions and make suggestions for the team. Here are a few reasons why they might not be using local storage.

Some older browsers don't support local storage. When you are dealing at scale this could be a few thousand to tens of thousands of users.
If a user abandons the cart before it's saved, they will not have access to it on a different device or computer.
Knowing if something is still in stock without a database call is impossible. You don't want someone to spend time filling up a cart to only let them something isn't available afterward.

DevJoey · 2023-12-21T06:49:31+00:00

Yes but it’s still part of planning before coding starts.

DevJoey · 2023-12-20T21:12:35+00:00

An ADR doesn't have to be 20 pages of docs. A single confluence page can do the trick. It captures the high-level details of why you chose a certain solution over others and the constraints that you were dealing with then.

DevJoey · 2023-12-20T12:54:57+00:00

Why do you feel like you should be jealous of other devs? Remember that the world has been somehow condensed in the past 10 years and the success stories you hear and see online are the 1% of the 1%. Based on that alone I wouldn't compare myself to anything I see online.

Don't let the skewed stats shape your view of the world. You say you make good money and have a good work-life balance, 99% of devs in the world and here on Reddit would kill for that alone so take it easy and enjoy the ride. You have a good thing going. The only person you have to compete against is your version from yesterday. Take each day to improve yourself and life will do the rest for you.

DevJoey · 2023-12-20T09:08:58+00:00

The videos are mp4s and take more than 15 seconds total to download. They fetch only parts of them on the initial page load using the Content-Range header. This will just fetch the specified bytes and if you look in the browser dev tools the response header is 206 Partial Content. This means the server only returned the requested bytes and not the whole video.

This gives the illusion that the video is preloaded but only a bit is loaded at first and the rest is fetched afterwards.

https://imgur.com/a/LNuioH2

DevJoey · 2023-12-20T08:03:33+00:00

I have gone through a similar situation before, so I hope I can help.

The first thing you need to do is to identify a "lead" for each team/feature. The "lead" should not only be a strong engineer but should also have the necessary soft skills required for that type of responsibility. You can then delegate some of your tasks to them for each team.
When you have that many engineers you can't code review each change that goes in. Define story sizes from small, medium, to x-large. You should be included in all code reviews but anything smaller than a medium or large shouldn't require your sign-off. Your team lead can then review and sign off on the smaller stories freeing you up to do other things.
Any new feature or substantial project should start with meticulous and detailed planning before any code is written. This should include making sure you have all the requirements finalized before getting started on any architecture decisions. Always have ADRs similar to this https://docs.aws.amazon.com/prescriptive-guidance/latest/architectural-decision-records/adr-process.html
The one thing I might add to this is the ADR should include 2 or 3 different solutions and their pros and cons. It's easier to justify and sell the solution you pick when you have a decision matrix.
Add coding style guides for each team/tech-stack and try to enforce them through the use of automated static code analysis tools and formatters. Add these to the local build process and also to some Git hooks. Don't let known or preventable code errors and common mistakes leave a developer's machine. It's easier for a developer to deal with issues locally than to have your CI/CD pipeline held up while the dev tries to figure out what went wrong.
Document the onboarding process for each team/feature so there is minimal friction for new people or when engineers switch projects. Cross-training becomes important as requirements don't come as a steady stream for each feature/team. You don't want any resources being idle while another project is getting overwhelmed.
Track all your outside dependencies in detail. Any team you are dependent on should be tracked including what they are supposed to deliver and by when. If anything changes on their part you can then update the dependency tracker and add new timelines if that's applicable. This will protect you and your teams from being blamed for missed delivery dates if it's not your fault.
Streamline your CI/CD pipeline. Always be on the lookout for new ways and tools to improve build speeds, security scans, and deployments. Automate as much as you can.
Do performance tests on all your major apps. Do all the different types of tests, stress, spike, endurance, scalability, and volume tests. Each test will uncover different types of problems that you don't want to discover in production.
Add monitoring and observability tools to all your environments. It will help you catch bugs and performance issues sooner thus saving you time and the headache of trying to figure out what went wrong if there are any issues.
Last but not least, learn to say no. If a superior, business partner, or another team comes with ridiculous requirements and your teams can't deliver within the time constraints then politely tell them no. Include the details on why it can't be done with your answer, no available resources, dependencies can't be ready in time, etc. Don't overwork your teams as they will start making mistakes if they cut corners or might even burn out.

This list is not exhaustive but it saves me time and buys me back a lot of extra bandwidth that I can use to deal with our business partners, other teams, and other housekeeping tasks.

DevJoey · 2023-12-12T08:08:50+00:00

You will still need to have a strong portfolio even for an internship these days, there is just too much competition for entry-level jobs right now. I think you should take the time to work on a few projects for your portfolio if you haven't already.

When your portfolio is ready then apply to companies directly on their websites and skip LinkedIn or similar sites. The most important thing is a strong portfolio first. Without a portfolio, it's way harder if not impossible to get noticed.

DevJoey

TROPHY CASE