I mostly get PTSD when listening to music while coding. Honestly, I've seen so much code it all just blends together in matrix-like data streams, and I rely on IntelliSense to translate what I'm typing into the right language. In all seriousness, yes, any pattern that gets stored in brain can be clustered with useful information. But because we're bio-mechanical logic engines enslaved to a cabal of gut-bacteria getting consistent high fidelity is typically an issue. Don't think about it too much. You can increase fidelity to useable levels by training your rote-memory on a finite data-set, and piggy backing on that as an encoding scheme instead.

Real-time in manager-speak translates to roughly 10 seconds actual. ;P

Here's an idea: don't do that. If you want a minimalistic system to fetch real-time data streams, don't use a developer and consumer oriented OS. In my professional opinion, it's not worth the effort, specifically due to security constraints. If you want to go down that path regardless, perhaps because you already have an extensive security infrastructure in place that relies on provisioning updates to Windows-based machines, use Windows IoT and don't strip anything update, internet or security related. If the previous iterations of Windows Embedded are anything to go by, it will still be a large amount of work for no tangible gains. Just use Linux instead.

While I do understand your take on the matter, and don't mean to undercut it in an unrespectful manner, I am gonna challenge the notion that classes could be based on either real or abstract entities. I'm 20 years deep in OO-design and the major problems I keep coming across with class-based designs, all originate from classes being based on non-concrete entities. As an iron rule within my own team, I demand that all classes are directly based on either concrete entities or the pre-defined abstraction layers we've all agreed upon (so services and data models are OK, helper classes or business objects are not OK). Over the years, this has been the magic sauce that made my team come out on top with regards to velocity and code quality. I'm playing with the idea of writing something on the topic eventually, because I think it's a relatively novel POV within our sector. I do like to use a quote from the matrix to highlight the underlying sentiment: When it comes to abstractions, "The problem is choice".

I feel like you're describing an FA instead of a BA. BA's basically mess around by "identifying" abstract business objects of value, typically for internal reporting to a board or a director. Then they make requests for implementing a business layer that respects and reports on those objects. This is done to give the board members a false sense of security. In reality, however, business objects are figments of someone's imagination made concrete, for no clear reason other than to show graphs or metrics. This in itself can create value if your brand narrative relies on fancy graphs and is mostly B2B oriented.. but the exact same result can often be achieved by measuring actual objects, so I fail to see the point of mucking up a code base for imaginary points of interest.

Hard no. Allocating resources to BA's is a mistake. They do not add value for the end user and they increase the technical cost, while reducing the individual ownership for everyone involved. I've seen enterprises run successfully with and without BA's, and without them there is less churn, more individual responsibility and less sunken costs in reports and metrics for internal use only. They do not add value and they do not contribute to getting the work done, so why waste the resources. Hire more support and customer training positions instead for a much better ROI.

In all seriousness, it also tells if a written number is even or odd. I've seen worse.

I have one person in my team who will insist on doing things their way, because of clean code and readability. It's such a moot point, IMHO. Practically speaking, you should stick to the following: Structurally, you should keep the cyclometric complexity low --> you'll have cheaper A/B testing in the future, which is a good fallback strategy for unforeseen issues of all sizes. Syntax wise, just copy whatever style is prevalent in the code-base already, and reduce inconsistencies --> cheaper refactoring in the future. Quality wise, you should always aim for less lines of code, without resorting to ANY advanced language techniques --> less reading to understand the code, less esoteric bugs. Just do those three things to drive costs down and quality up. Everything else is pointless. The compiler doesn't care about the look and feel of the code and the user definitely doesn't care. We should take a hint and stop caring so much too.

All of them. Person 1 is lying, because person 1 speaks first, and the statement can't be truthful. Person 2 is lying, because person 2 speaks second, and the statement can't be truthful. Person 3 is lying, because person 3 speaks thirdly, and the statement can't be truthful. Person 4 is lying, because the statement can't be truthful.

A.k.a. namespace pollution. If you import a large amount of classes/functions, that you do not know the name of, you end up with a higher risk of running into namespace collisions.

Definitely the first one. Low level functions should only do things, preferably in a class that can get mocked during testing. High level functions should decide which things are worth doing, and are prime targets to test.

Please reconsider, if the virus keeps circulating it might mutate beyond our ability to vaccinate against it. That would suck so bad.

The US is kinda broken. There's no single source of truth everyone can agree on, and it amazes me they're still somewhat united despite of that. It's like, they don't get along, they don't believe each other, but they're also fundamentally too lazy and don't care enough to do anything about it. So, surprisingly, it just works.

I've had COVID-19 twice already, and I got my first Pfizer shot a couple of days ago. There are no safety considerations regarding past exposures. There is an advisory in effect to not get the shot WHILE you have COVID-19. Either way, I live in a country of 11 million people with a very honest reporting and after setting about 8 million shots, we've had 467 complications and 21 deaths in total. We rule any death that might have been vaccine related, as guaranteed vaccine related, for transparency reasons. I live in Belgium, and we're the only country on earth that does that, because, when our Joe average reads things like that, we think: That's a pretty good result, I'm gonna sign up for my vaccine today. Honestly, the vaccine quality is great, and the health risks are very minimal. There is no reason to not get a vaccine.

Be honest, how long does it take to learn a framework nowadays? In the most extreme case, a week. In the vast majority of cases, a day or two. As an example, let's look at Vue. Why would anyone use Vue? --> It contains data-binding boilerplate code, so you don't need to update every component manually when data changes. How do you learn it? --> You follow a 5 minute tutorial on their website. How do you master it? --> You take an hour to look at all of the user-reported issues on github and you avoid the parts that don't work. **The More You Know**

My most valuable skill: I can unlearn and relearn anything. Courtesy of my mother's genes and her terrible long-term recall. :cool:

On the web, JavaScript needs to die and browser based work needs a compilation step, and an actual debugger. Meanwhile, transpiling, polyfilling, binding-frameworks, browser extensions for debugging.. all spring up to extend the lifespan of JavaScript, because JavaScript is still the king of the hill. But, ever since WASM got into the evergreen browsers, there has opened up an alternative path, and now a bunch of frameworks are trying to take the hill and kill the king. On the general UI front, people are trying to streamline UI workflows, so components actually work across platforms. Which is, ironically, something we almost solved 3x over, but because big corporations hate each other they keep sabotaging every attempt at unifying the UI stack. As a result, lot's of small initiatives spring up everywhere, which either die out over time, or get bought up and die out over time. On the scientific front, Julia has created a new programming paradigm, and it seems like those ideas still need to re-invent themselves a couple of times. On the low-level front, thread-safety is all the hype nowadays, because concurrent threads are a pain in C++, mostly because you need a lot of fault-free boilerplate code. And after writing state-machine after state-machine to manage your threads, you kinda get tired of going through all that for nothing.

I'm not gonna hint at the sector, but I know of a vendor that sells pretty darn critical software packages, and they get secured by a physical hardware key. Under the hood, it uses decentralized DB shards that connect to a central authentication DB, and only when the entire network is properly meshed, does the hardware key authenticate. And if you don't have enough money for a key, or a certified authentication server, you can just access the DB manually and turn off the security. Yeah. Great design guys. 10/10

Me too! .. mostly because it worked well for me in 2003 and googling a makefile takes about 2 minutes, so why change?

Edge is better though, that's why I highly recommend it to friends, family and total strangers alike. :D Edit: Chrome eats all the RAM Edge does not and has better privacy and security features