No we’re not eager. Paperwork is just part of any job.

deleted by creator

True, but at the same time its very possible to go too small. A bunch of one line code reviews can really slow progress easily.

My thoughts are spending too much time on the computer is bad for you, and once you find a good long term job, you dont need to learn so much. Youre 2 years into your career, hopefully you’ll find a good fit.

Knowing how to Hello World in ADA is not very helpful, try to find in demand things to learn. There really isnt that much.

Well, that, and programming itself is starting to slow down.

Make one post a day for a few months

I would argue that HR has a very specific role in hiring, namely background checks and verifying that the resume matches reality.

It doesn’t generate them, you still have to write them. Ignore the marketing, look at the actual docs, same as any other framework.

There’s a few other frameworks, I just prefer playwright because I’m used to it.

Don’t. You really can’t for most of it. At best, you can test whatever utility functions you have. The FE can and will break more in design than anything else, and that will never get caught by tests.

That said, try a wholistic approach. Playwright requires you to run the back end too, so you get a proper test suite going, instead of jest or whatever.

A very limited amount.

YES!

At that point, you get your team lead to go in the repo settings and unblock it.

Eh. Not as good as Gloryhammer.

When the metric is lines of code

I swear Im a decent coder, but fuck me if kubernetes and that whole ecosystem just confuses me

Half the problem is that js was made over a weekend and we cant seem to come up with a different solution.

Typescript is great for catching long standing bugs in old legacy JS.

Pretty much, just file system is boring work

Front end and back end are different enough that you can really specialize in one or the other. They take very different mindsets. I know how to make css obey, I don’t know how to make sql performant. Its possible to have both, but not as well.

For every front-end dev, you need 3 back-end guys and a designer.

Programmers are not bad at our jobs, its just not a mature disclipline yet.

1. Theres too many skeletons on the front end. We need unique names.

2. Im not sure why this library exists.

How do i do this? I have an android