I disagree. When people typically pronounce, for example, "1800s," they would say "Eighteen Hundreds," with the plural suffixing "hundred," implying a period of far longer than a decade. If trying to reference the decade following 1800, in conversation I would say "the Eighteen Noughts."
I don't know what sort of localized English you speak, but that is not how it works in America. [Based on past comments, you may be located in Australia. I could certainly understand if there are local phenomena in your language there.]
If we say "In the nineteen hundreds..." we mean 1900-1910. If we said "In the ninteen fifties" we would not be implying a 50-year period, would we? If we said "In the nineteen nineties" are we implying a 90-year period? Do you see how your logic immediately breaks down? Is it mere accident that "the ninteen tens" is a ten-year period of time? Yes it is...
Your assertions and these patterns of speech are just bizarre. I don't know anyone who says, or writes, "the Eighteen Noughts" at all. It is not a thing for scholars of history, for sure.
For a while it has been debated how we'll refer to 2000-2009. Because in different centuries, those initial ten years gained unique names. Some people want to call it "The Aughts" or "The Noughts" but I don't really hear people referring to "The Two Thousands" yet, at all; it's largely "The 21st Century".
You might want to have a look at Remix [0]. I haven't used it extensively myself, but it does claim to handle errors well.
> Route Error Boundaries keep the happy path happy. Each route module can export an error boundary next to the default route component.
> If an error is thrown, client or server side, users see the boundary instead of the default component. Routes w/o trouble render normally, so users have more options than slamming refresh. If a route has no boundary, errors bubble up. Just put one at the top and chill out about errors in code review, yeah?
I'm genuinely curious to find out whether anybody is surprised by this given that it's a language model that has been trained on almost all of the information and the data on the internet will beat human accuracy on tests - computers can retain memories and data a lot better than humans can and models like these simply have a lot more non-unique information than humans have consumed in their lifetimes.
I honestly have never loved Microsoft but I can definitely see that they are making some great business decisions. I love Apple but they need to up their game. AI has been around for over a decade but we are definitely going to start seeing it everywhere. I know big things are coming. (that's what she said)
I've been a self taught designer for as long as I've been a self taught programmer.
Initially I started out building basic 2D games in GameMaker Studio which got me to start to draw pixel art (just basic stuff) so I'd say if you want to make a game maybe start out with that.
In my honest opinion I believe that design is quite mathematical and structure.
Definitely download Figma and do your best to learn the basics - it's an incredibly useful piece of software and on the internet there's plenty of challenges and resources that you'd be able to do to get the skills of Figma.
I remember I did a "30 days of design" challenge a little while ago which sent me an email every day with a concept to design. I'd try and find that and see if it's still up and running.
I wish you the very best with your endeavours! Welcome to the design community <3
I'd definitely start by taking a look at the React Navigation documentation. It's a library that provides a lot of tools for native navigation and page routing. In my opinion, this is the most important library (apart from React and React Native) to learn to have the skills to be an entire React Native app.
From the React Navigation docs they suggest taking a look at these resources to get the fundemantals sorted:
1. React Native Express - teaches all the basics of React Native
2. Main Concepts of React - Allows you to understand how React works
3. React Hooks - Provides specific reference towards using hooks in React (they're addictively useful)
reply