web development in Canada isn't too much different from the US
we just use "visibleEh" instead of "isVisible" and instead of state it's province management
In this new age of AI and copilots, we are reimagining all of our products to take advantage of the opportunity ahead. Today we announced two big things.
First, the new release of Windows 11, significant updates to Microsoft 365 and Bing & Edge, and two new Surface Devices.
And second, we revealed our vision to deliver Copilot, your everyday AI companion – to help people be smarter, more creative, more productive, and more connected to the world around them!
Be sure to check out our blog to unpack all of today’s news: https://t.co/S0uSXDwiNB
If you had a small and simple domain, and a relatively small number of concurrent users you needed to support, you would probably expect to have a relatively simple architecture, with only a few moving parts, and not that many dependencies.
If you had a large and complex domain, or multiple domains, and needed to support many thousands or even millions of concurrent users, you wouldn't be surprised by a more complex architecture, with more moving parts, and a larger number of dependencies.
One of the problems with current trends in web development is that the exact opposite is often being promoted. You have people promoting complex architectures and setups, with lots of moving parts, and tons of dependencies for scenarios where the business domain is very simple and only a few users need to be supported.
I use the term "complexity peddling" to describe this, and it's very destructive.
I encourage you to resist the urge to give in to social media pressure that insists you need to use X framework or tech stack for *all* your projects. Think for yourself. There's a lot to be said for common sense. Evaluate the specifics of the situation carefully and choose the simplest possible solution.
learned from @jitl today that https://t.co/XpFaumUI1T exists – it has these options for the call tree which I have wanted for years in a JS profiling UI
We just released TypeScript 5.2 Beta! Check out
- 'using' Declarations
- Decorator Metadata
- Easier Tuple Type Notation
- The "Inline Variable" Refactoring
- Comma Completions in Object Literals
and more! Try it today!
https://t.co/KXlaBsYxz1
Fluid Framework 2.0 Alpha is now available with SharedTree and an improved developer experience with the Fluid Developer Tools.
Learn more https://t.co/AdczLPWMWK
#Microsoft365Dev#FluidFramework
In 2018, an Amazon employee shared the company’s “7 Tips for Business Writing.”
They’re a must-read for anyone who wants to write more clearly.
1. Use fewer than 30 words per sentence
Constraints drive clear thinking.
And the best constraints force you to use less words, not more.
If you can explain something in simple terms, you likely understand it well.
2. Use subject-verb-object sentences
The goal of writing is to transfer your thoughts to another person with as little lost in translation as possible.
It’s a big game of telephone.
The simpler your sentences, the more accurately your ideas will be translated.
3. Replace adjectives with data
“Customers love Prime.”
“Customers with Prime spend on average 3x more than those without and we retain 90% of them year over year.”
Specificity leads to clear results and quick decision-making.
4. Pass the “so what” test
The reader should immediately know what action you want them to take.
Make sure to answer who, what, and when.
Otherwise, you’ve wasted your time and the reader’s.
5. Eliminate weasel words
Most weasel words are adverbs.
“Nearly,” “Significantly,” “Almost.”
These words are imprecise. They may mean one thing to you, and another to your boss.
Get rid of them.
6. Avoid clutter words
Utilize → use
In order to → to
Until such time as → until
Due to the fact → because
Getting rid of clutter focuses your message on the parts that matter.
7. Avoid jargon and acronyms
Companies are littered with internal jargon.
But this excludes new employees and anyone external to the company.
When wanting to use an acronym, write it out the first time it’s used in any document.
Clear > clever
***
The best marketers are relationship builders — strong internal alignment separates good from great.
So I got interested in Amazon’s writing.
Because writing is communication and communication is alignment.
Follow @TheMarkJung for more content like this on marketing and media.
JavaScript import-maps are now supported cross-browser! 🗺️ https://t.co/el56VvP1XZ
<script type="importmap"> can define a mapping of external module names to their corresponding URLs, making it easier to use in your code.