it successfully brought you the error.

stick it to the 2000 management men.

@Drunkzee i think it's also dangerous to only do or be one thing. You start to think that everybody that doesn't do your reality is missing out on something.

But it's the 21st century. You are either selling courses and being an influencer for bird clothing ( or any other niche thing) or you are nothing XD

9 euros an hour? I've paid more per hour just for cleaning my house. And I live in a poor EU country. Even if it wasn't for the salary, it's too much workload. Why do people think that other people's health doesn't matter?

Studying is overrated. But thank god most people believe in it. Less competition

@StopWastingTime No college degree, came from arts high school, now I start projects from scratch. I have 2 years of experience:

Just quit.

Your shitty job is consequence of your personal problems and personality. Read, improve yourself, and for god sake just quit. We're in an industry where better job offers land on our LinkedIn every god damn day.

Packages in package.json are only included in the final bundle if you actually import them in the code. If they are not imported, there's no way they will magically appear in the bundle. Basically, you just removed 32 entries, but not actually made it faster. Also, if you import something but never actually read the value returned by the import, webpack is smart enough not to include it in the final bundle. Use webpack-bundle-analyzer to tackle what is actually taking up space in the final build. Performance problems in angular apps can be easily solved by just start lazy-loading certain groups of routes.

That's because of WebP pictures, the replacement format for JPEG and PNG. All the browsers support it (even Edge), except Safari. Most websites including 9gag already use that format. Gatsby solves that problem by falling back to JPEG on Safari

@ZioCain Yeah I know. It probably uses NDK underneath and already compiled stuff in the best way possible. Just don't mock webdevs. It's actually hard being a webdev because you have so much things to deal with in an ever changing environment (web browser) with so many things happening at the same time (async stuff)

APKs contain Java byte-code, which can be even more optimized by using ProGuard (which minifies code by shortening byte-code encoded names). The option to enable this in Gradle is called minify. And it's enabled on most projects.
Don't try to sound smarter than others. There are no stupid questions.

I don't put semicolons. Discussions like this are for pitiful developers who focus more on whining than to actually do proper work for people. Just do your job, and make code easy to change. that's it.

I like how some here feel superior by denying PRs just to bitch about semicolons. Seems like it's the only thing in life they control.

@PappyHans There is no native translation for the Javascript code. React Native runs Javascript in development the same way it runs in production: using Chrome's V8 engine. The only difference is, instead of rendering <div>s, it renders Android Views. And you're not going to test what's already an atomic unit in android development. So, there isn't a JavaScript conversion to native code.

Also, most company projects do not require multi-threading, and if they do, you can do it in the few lines of native code you need for that action. Also, managers prefer to tweak stuff right on site than to wait for changes to compile. That's why time-travel is good in these cases. You can go back and forth and review the flow with your manager. Also, the guarantee that they can quickly have a web developer working in the mobile app makes them more at ease.

Remember that the world is a small place. If it goes wrong, people talk, especially recruiters. Do not hit on people related to work :/ This kind of behavior also signals that you don't have other options in the dating department.

@PappyHans memory management, threading, views (using CSS-in-JS abstracts me from having to learn XML or other native styling methodology), async callbacks, state management with time travel (something like Redux is hard in native languages), HTTP requests. Testing is also easier. All these things are limitations in native code. I can't remember more.

@terriblecoder Anything that has a plus is good for me. That is why I only jump ships when something is already stable and has enough tooling.

Like the Flow vs Typescript thing

@PappyHans That is why it's best to treat the UI as "a web page" and have the JavaScript engine abstract a bunch of native limitations, and only write what you need in native code.

@terriblecoder Also Svelte does not have hot reload. I want to be in a call with a client and be able to show front-end changes without having to wait. Like a designer

@terriblecoder True. I just get a little bit mad that people still write code using old tools and then rant about not being able to adapt to stuff. Because someone is going to maintain that stuff. That's why I completely decided I would never get back to maintaining projects.

@PappyHans Yeah. Mainly Jest. I don't bother to test native code, since uncaught exceptions are always logged. Heck, there are apps I don't even test and they run fine (of course, with the strictest level of Typescript, and with Sentry running)

Hybrid apps help in development time even for a mobile developer. I know how to write Android apps, but always choose React Native or Ionic in order to have most UI and state be cross-platform and have hot-reloading. All the heavy-lifting tasks are then provided by mere snippets of native code. This way, you can have most developers working with JavaScript, and call a native developer when special native code is required. This also reduces costs.

@TitanLannister Sounds like someday we will have a new area: testops. Not kidding. Your friend is right.

@Jilano Nope. Wordpress does not have hot reload (watch changes without need for reloading page), and needs a server. We also have some info we want to get from an API at build time, and auto generated robots.txt and sitemap. And also some cool CSS effects

Made a website in 1 week, with 94% SEO score in Google Lighthouse, all in Gatsby, React and Typescript. And it also has automatic asset compression and progressive loading for pictures without having to write any code for it.

It's not the tools. It's the guy using them.

Also, testing is like graphic design. If companies can cut it, they will. Some of them don't even remember that they need something like that.

Also, developers following TDD already test and automate stuff by themselves, so, less need for testers.

-> it's getting more and more automated till one day, few testers will be needed
-> What is not automated is boringly repetitive.
-> No creative part. You only test what others created.
-> People from other areas can test stuff, so offer surpasses demand.
-> It's hard to sharpen programming skills since you'll barely code, and what you'll code will be in DSL or proprietary.
-> Low salaries

Good points:
-> Easy to get in. That's why everybody from engineering that didn't get a job does testing.

Because sound, be it audible of not, causes damage to your ears if you are exposed for a long time. Also, some people can listen to high pitched frequencies.

Your job as a developer is always to start with the things you don't know. And move to the next one, and so one.

The sweetspot in development is learning new stuff. Cutting-edge developers are the ones who are always jumping to tasks they don't know about. Average developers keep doing what they always know with average pay and average mental activity.

If you are always learning new stuff, you will always be needed, and you will call the shots when something new needs to be implemented. Also, you'll be better just by surrounding yourself with new people and new techniques. You won't fail. I used to be a graphic designer. In two years I'm doing AI stuff. There's is nothing to difficult to learn. In an emergency, the adrenaline spike will make everything happen.

Here's another advice to keep your mental health at work: learn to architect and start projects from scratch so you can work at startups and avoid contact with most developers

@reij How's that working out for you? Have you got enough amount of "bitches"? Is that a measure? This is why most developers are lonely clowns, getting replaced by people from other backgrounds.

Also, I don't exercise, and I haven't saw a need to. It's something I'm not proud to say. Let's just see where this goes.