hussainbilal
1. Always takes props but always returns null. (Useful for Todo comments that contain jsx code snippets that don't render)
2. Or, always takes children and a single comment prop, and always returns children in react fragment. (To associate specific comments with specific jsx snippets)
You could even have multiple exports for them. (I.e. Todo vs Warning vs. Comment)
Maybe combine them to make a Spring-like framework, but for C?
Long standing non-changing specs and standards should be married, and with children.
So realistically, only Commit (under Browsing Git repositories) and Code review actually matter. Lighthouse metrics don't matter much at that point (if I'm at the PR stage I will put up with an unusual delay to get the PR through).
I think that's what you're seeing with these metrics. Dev's don't care about a repo's browser experience. They care about the terminal/desktop-app experience.
https://fs.blog/knowledge-project-podcast/jim-collins-2/
Long story short: Happiness is derivable mainly either through relationships or transactions (can read this as opportunities you create).
The problem: Deriving happiness through transactions doesn't scale beyond you and your abilities and your time. Deriving happiness through relationships does scale.
Coming back to your question: conversation and listening skills are relevant to both. There is more certainty in using these skills towards transactions (think sales). But you should be putting these skills towards relationship building as well. Mainly because other people may be (and often are for strong relationships) happy to help you out for nothing or very little in return mainly because of a trust that if you're able to you will help them for some future endeavors / dilemmas. This can be seen as an investment towards leverage (think sales growth).
The podcast doesn't take the view I wrote here. The podcast conversation is more interpersonally oriented in its view, but the conversation is oriented towards CEOs.
- WebAssembley (which other, controversially better or at least more adopted languages also target)
- Javascript's spec. is not time invariant (https://github.com/tc39/proposals#readme)
- Typescript isn't the best solution (There are better less adopted solutions providing types, like Elm, Rescript, or Purescript)
For Javascript, the real solution is hygienic macros and contracts, but because `eval()` can't get no love or safety on the browser side, everyone on the server-side has to suffer.
Ironically, introducing a fake compilation step where Javascript transpiles to Javascript (not like babel.js which targets older JS, but literally just the same lang spec) is the way to side step the `eval()` problem, lol! (expanding those `eval()` in a fake compile step)
Based on what I've read, while Hashicorp tools may look like their only contribution is platform agnostic tooling, a deep dive into the docs reveals a focus on dynamically changing architecture and providing tooling to scale dynamically changing architectures in short time scales to any number of resources (i.e. not just machines / VM / containers / compute resources, but resources like users, user-generated resources, user-generated secrets etc.)
My impressions thus far is that Hashicorp is aware of the variety of alternative tools, that's why their certifications / training / professional services are only available for the tools truly core to supporting dynamic architectures : Terraform, Consul and Vault.
https://www.hashicorp.com/customer-success/professional-serv...
https://www.hashicorp.com/customer-success/enterprise-academ...
1. The majority of programmers/IT/Tech-workers are young (<=3 years of work experience). They don't have enough experience to know what's good (or even what matters) for their craft. (i.e. no one should care about programming language because often you don't get to pick it. Your employer does.)
2. The majority of programmers aren't in North America. They're in Europe and Asia. So there is a linguistic barrier. And this linguistic barrier will get hit because the majority of programming work is done in English. So many of these young non-north-american programmers are trying to polish off their English in these online forums. (So expect people to talk past each other or losing things in translation or flat out misreading subtext)
3. The majority of employers of young/non-senior programmers are not product companies. They're services, start-up, IT or financial companies. Services and start-up companies are sales focuses. So a programmers career path will always ultimately lead to sales to some extent. IT and Financial companies have a larger focus on infrastructure or data reporting. (i.e. majority of careers force programmers to become something else, like leaders. So there is a very real brain drain away from the craft)
---
for OP:
The simple solution to what you're observing is to stop reading online forums. Instead watch youtube conference videos, read books, and listen to podcasts. When programmers don't have anonymity, the quality and relevance of the content/discussion go up dramatically.
---
Irrelevant comment:
I think the reason for all this is because anonymity allows insecure/young programmers to test waters before asserting their ideas in the workplace. This is most likely what all the young programmers being pushed towards different careers are doing. They're looking for a magical piece of information that will force a business to align to their own career aspirations rather than changing their own goals to better align with their employer's objectives (i.e. a very uncomfortable sales-oriented self-transformation).
I wrote an article about this from the perspective of avoiding software technical debt, but I have to admit, this article does a better job on explaining why it works than my own article (╯°□°)╯︵ ┻━┻
https://connected.io/post/how-to-avoid-technical-debt/ tldr: You can find overlap or convergence by applying PCA on a trade-off matrix.
This article is right for the wrong reasons. AI/ML (which approximates optimization problems due to inputs not being clearly defined) is not required for the replacement of middle management (an actual optimization problem with clearly defined inputs).
Based on the title, I thought they were going to talk about how all operators should be expressed with 3 characters (i.e. `:=:`, `|=>`, etc.) or how all reserved words should be 4 character words.
The idea of an atomic habit is that there is no disconnect between a habit and the objective you're aiming for. So in this case, the habit was not to learn a new language, but just consistently and constantly engaging with French. When I hit a wall, I doubled down my atomic habit to a simpler macro-french where all my past knowledge would still be applicable due to the etymology heavily influenced from french colonization.
I have no suggestion for artists, because the point is to pickup phonetics under variation. If you listen to the same artist, you're only picking up their way of speaking.
i.e. I'm guilty of playing dubmatique and maitre-gims on loop. Did nothing for improving my ability to parse a spoken french sentence in real-time. I just ended up memorizing the lyrics.
I suggest listening to pop music on shuffle, even if it's not your cup of tea. Pop music is usually very good with enunciating words. Additionally in my experience, pop music lyrics align really well with a language's IDF.
Example 1: start learning a new natural language, and also switch all your social media feeds to only provide content in that language. You'll either lose interest in learning the language and start withdrawing from social media, or your unbreakable habit will sustain your new language learning habit.
Example 2: I listen to a lot of music. I don't feel right unless it's running in the background. So I tried learning french and listen to only french pop. It worked for a few months, but then I hit the problem of not being able to pick up spoken (not written) french and parse its grammar while also trying to pick up the phonetics of native speakers. But I then learned about creole and its more flexible and simpler grammars and phonetics. I was able to start thinking in the language using french vocabulary. So I pivoted my habit to learning Haitian Creole and listening to Haitian music.
Edit: and you get typing validation for free by running your yaml options through a yaml schema validator should you choose to do so
I think hush is going in the wrong direction. The majority of shell automation is associated with running IaC and container images / orchestration tools.
Shell scripts don't need to follow functional programming or OOP. They need to be container-oriented / VM-oriented / image-oriented with a conformation to YAML notation as this is already the adopted norm for containers and IaC.
If you're not only changing config but rewriting templates, then you're already fighting against the framework and deviating from best practices. Don't do that.
My understanding is that if you're regularly rewriting Spring provided templates, then you've likely hit the need for Spring AOP, so the DI magic can be kept manageable.
If you're a consumer and you're hitting this issue (needing to regularly provide own custom templates on the client-side), then you've likely hit the need for Spring Integration on the server-side.
If your BMI is high, then Keto + intermitten fasting + calorie deficit is your best bet (I use to be 300 pounds and lost 50 pounds in 3 months.)
If your BMI is low, then regular cardio (i.e. calorie deficit at the cost of increased hunger) is your best bet (how I got myself down to 200 pounds.)
If your lazy, then strength/weight training (i.e. increased muscle weight to replaced fat trading off with an increased metabolism) is your best bet (how I plan on getting to 150 pounds)
(Edit: Also, the english my code comments deserve) (Edit 2: and my commit messages)
So its probably not so much propaganda. It's more like if you already know a trade and are interested in knowing more or working at a higher-order than what you already do, there's likely a STEM field for you for exactly that pursuit.
i.e.
- Construction worker? Mason? Civil engineer
- Electrician? Electircal engineer
- Mechanic? Mechanical engineering
- CNC Machine operator? Software engineering (if you're interested by the machine itself) or Industrial engineering (if you're interested by the workflow)
So I would imagine anything single-threaded would not require it.
Though admittedly, the only modern application or program that I can think of that would be single-threaded is a CLI command