I’m surprised, I would love to work in Java 20. Do you have any particular pain points with it? Or is it just that you’d rather be using something else?
Have you actually tried that? It just works. Win11 isnt much more than a big Win10 feature update. We’ve updated a few hundred machines across several customers and they rarely required manual intervention.
Well–well look. I already told you: I deal with the god damn customers so the engineers don’t have to. I have people skills; I am good at dealing with people. Can’t you understand that? What the hell is wrong with you people?
Unless there’s a bug. Then it is my code and I have to fix it. Immediately. No, I don’t want to discuss my thought process for “why I made that decision” I want to fix it. Why are we having a chat about milk pouring technique while it is dripping off the fucking table. Prod is burning and you want to fiddle! (Meanwhile this is a minor bug that nobody has ever actually complained about but just the knowledge that it was my fault…)
Increasing the CPU optimization by 0.02% does seem crazy to me. If you’re going to spend time working on something, make it worthwhile. Also, isn’t while(true) {print(money)} Microsoft, Apple and Amazon:s business model?
It’s because it has to run in a browser. (Why would I want to write JS that runs outside a browser? Rhetorical question. Don’t answer that.)
I use no JS dependencies. Zero. None. No jQuery. No React. No VUE. No Typescript. Nothing like that. (Unless you count as “JS dependencies” a) a minifier (but not one written in JS) or b) browser builtins.)
I don’t use any ECMA6 stuff. (Who asked for classes anyway?) Though to be fair, that’s definitely at least partially because I have yet to even really look into what’s available.
I love callbacks and closures.
I keep my global scope tidy, though I do store some things in the global scope. (Typically one or fewer global variables defined per JS file.)
I don’t use prototypes. Just because I’ve never found good uses for them.
I do believe there’s a beautiful language living inside JS. It is quite pleasant to work with. But not the kind of thing I’d want to write “real software” in when there are alternatives like Go or even Python.
We used to use jQuery because there basically wasn’t a decent way to do a lot of things back then. Like selectors for instance.
Many of its best features have been absorbed in JS to the point vanilla is a much more approachable choice now.
The reason react and Vue are so popular is that any decently sized js app quickly becomes very hard to maintain. Or at least becomes time consuming to maintain. This is generally down to its dynamic nature.
Yeah, I agree that jQuery used to be pretty necessary for some pretty basic features in JS but is kindof obsolete now-a-days.
I don’t agree that any codebase that doesn’t use framewok X or Y will inevitably devolve into unmaintainability. If it does, it’s probably more because one isn’t following best practices. (Like the Unix Philosophy or SOLID (which functionally are kindof the same thing), DRY, ZOI, etc.) And no amount of frameworks can save you from that fate if you indeed aren’t taking steps to ensure the longer-term maintainability of your codebase.
You do you, but no ECMA6 stuff? I don’t use a lot of ECMA6 either because JS is at ECMA14 and continues to change. I can’t imagine reinplementing stuff on every project you work on, though perhaps your work is very different to mine. That said, treeshaking has really brought down the cost of imports and there are few occasions where using a custom solution over a reliable third party library is a good option. Curious to hear your thoughts.
Treeshaking imports (which, admittedly, I just learned about from some googling) assume that the JS you’re importing comes from another file (that the browser would have to fetch separately), yes? I believe that’s not a restriction of RequireJS (which I have experience with through my work but wouldn’t use on any personal projects.)
I’m just thinking performance-wise you’d get better performance by putting all of your JS in one (or a very few) files to be fetched from the server via one (or very few) requests. I am perhaps more of a stickler for shaving a millisecond here and there. (Which is part of why I wouldn’t use large JS lubraries. I wouldn’t want to make the browser have to load them.)
It’s very typical to import code from other files, but it’s also typical to have a minification step that essentially performs what you’re saying, compressing the files down into something more optimal. In fact more advanced solutions essentially stream the minium amount to users as needed, and compute as much as possible in the server side.
To be honest, I’d bet a lot than by not utilising larger libraries and their standardised functions, your code has a good chance of running slower. Besides, for the typical computer and network capabilities today, there’s a lot of wiggling room.
That said, for absolute tip top of performance (where experience is a trade off) you can find fun things like this, where groups do have to push for the upmost performance.
The paradox is that people don’t actually implement agile methodologies but rather try to shoehorn them into their waterfall mindset.
I’ve worked with a team of 10 developers (one of them tech lead) + 1 “PM”, using Test-Driven Development. The customer was the PO and was involved in the scrum process. When we had plannings, the TL+PM+PO had already prepared the User Stories for us, so they were easier to guesstimate. The customer/PO took part in reviews of deliverables and provided feedback. Overall it worked nicely.
Most other teams i’ve worked with were not agile, but fragile, waterfall in disguise. Never works.
Right now i work alone (and one QA) maintaining a legacy project plus handling the CI/CD maintenance and whatever else hits my fan. It’s agile when it suits the suits, otherwise they’re in charge, i have no say. Just yesterday i was handed a task by the boss of the boss, which will occupy me for a few days. I could go on ranting but i’d hit some character limit.
The paradox is that people don’t actually implement agile methodologies but rather try to shoehorn them into their waterfall mindset.
After several decades and several methodologies in a number of fields, I’ve concluded that very few actually think methodologies are useful. It’s always pick and choose or mix and match the various elements. This is all driven by the belief that my business is a special little flower and needs it’s own custom little process that only I can invent.
I know of a certain big company that has a bug report UI in one of their main products that literally goes nowhere, it used to go to a table in the db, then they removed the table since it was not really used and they wanted to get more storage, so someone quick fixed the bug report to go to a Google sheet
Nobody really checks that sheet and it is not automated or used for anything at all, the person that created that sheet was also deprovisioned some time ago.
Also since many things have changed the only thing that is pulled to the sheet is the first field to specify the category of the bug, all the descriptions, files, photos, logs and more granular items are just not going anywhere.
When this was reported the only reply from management was “QA will check it later” this was 2 years ago so…yeah
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.