|
Wordle 643 6/6
⬜🟩⬜⬜⬜
⬜🟩⬜⬜⬜
⬜🟩🟩⬜⬜
⬜🟩🟩🟨⬜
⬜🟩🟩🟩🟩
🟩🟩🟩🟩🟩
In a closed society where everybody's guilty, the only crime is getting caught. In a world of thieves, the only final sin is stupidity. - Hunter S Thompson - RIP
|
|
|
|
|
Wordle 643 5/6
🟨🟨⬜⬜⬜
⬜⬜⬜⬜🟨
⬜🟩⬜⬜⬜
⬜🟩🟩🟩🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 643 4/6
⬛⬛🟩🟨⬛
⬛⬛🟩⬛🟨
🟩🟩🟩🟩⬛
🟩🟩🟩🟩🟩
Get me coffee and no one gets hurt!
|
|
|
|
|
Wordle 643 4/6
⬜⬜🟩🟩⬜
⬜⬜🟩🟩🟨
⬜🟩🟩🟩🟩
🟩🟩🟩🟩🟩
started strong but one wrong guess
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
I owe an apology for all the CCC fans...
I totally forgot that today is the breast surgery of my wife's best friend and I have to take care beside my kids of hers too...
I just was so pre-occupied all day, until now (almost eleven at night), that I just forgot...
Most sincere appologies...
(Specially to @OriginalGriff and @petepjksolutionscom, the only two recognized I'm gone)
(The good thing is I have now a spare clue to post )
"If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization." ― Gerald Weinberg
|
|
|
|
|
Apology accepted - these things happen.
You might want to discuss with pkfox who posts tomorrow?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I prefer not to post tomorrow - it is my weekend...
"If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization." ― Gerald Weinberg
|
|
|
|
|
No worries I will post tomorrows
In a closed society where everybody's guilty, the only crime is getting caught. In a world of thieves, the only final sin is stupidity. - Hunter S Thompson - RIP
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: the only two recognized I'm gone They are the police of the CCC... it is their job
Hope your wife's friend surgery went fine and gets a quick recovery.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Nelek wrote: Hope your wife's friend surgery went fine and gets a quick recovery.
It is hers second - so recovery is a relative thing for her... But she will live, possibly long and happy life...
"If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization." ― Gerald Weinberg
|
|
|
|
|
#Worldle #426 4/6 (100%)
🟩🟩🟩🟩🟨↗️
🟩🟩🟩🟩🟨↘️
🟩🟩🟩🟩🟨↖️
🟩🟩🟩🟩🟩🎉
https://worldle.teuteuf.fr
no map
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
I think I'm jumping guns here and look at things that are too advanced and I'm always missing some steps and that blocks me.
What would be a proper course progress ?
html -> css -> javascript/typescript (?) -> react/angular/vue (?) -> asp.net core (?) -> database (?) -> ..
Am I missing anything obvious ?
unless really necessary, I don't care about look and feel of the final results as long as it work, so I only need basic html and css.
I think I should probably do a good javascript course as it seems to be the big technology that everything else is based on (more or less).
Thanks.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
|
Eloquent JavaScript[^] is a very good free online book. In addition, my suggestion is to just walk through some HTML-CSS-JS code already available on Github, in your domain of interest; I feel that will lead to faster learning.
|
|
|
|
|
Without a specific goal (project) in mind, I find it impossible to learn "something"; it's like memorizing history dates.
And once you start that project, it "tells" you what you need and when; or at least what you don't know and need.
But, yes, start with HTML and create your first static web site; hosted by someone else.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Depends.
Surprise, huh? Do you want to play around to build some fun private stuff, or do you want to make yourself attractive on the job market?
For the latter, I might be mistaken, but I think that just knowing JavaScript ™ aint gonna cut most cakes. Experience from frameworks will be required. React and Angular will be found/required in rather dated systems. NodeJS is fresher, but I might be wronk, perhaps that is closer to the back end...
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
Concerning Quote: Am I missing anything obvious ?
I think immediately about http, as this lurks behind everything in web development, and also, quite soon on this path, OAuth 2.0 becomes quite obvious to learn. Keeping focus and interest is essential, despite so many different technologies within web development ... 
|
|
|
|
|
What I did, after coming from WinForms, was start a new ASP.NET Web Application, either Razor or MVC will do.
It will gave you a working basic application with some HTML and CSS and some back-end C# code.
It's fairly basic, but you can copy-paste your pages or controllers and add new pages.
It made sense to me and you'll be able to build web applications fairly quickly, even without fully understanding it.
After that I applied for a job as web developer and was up to speed in a week (or maybe I applied first and worked it out later, can't remember).
You can work out how the back-end and front-end interact from there, find tutorials, etc.
You'll be able to search for the specific questions you have and you can move to completely decoupling your back-end and front-end if you want.
Forget about front-end frameworks like React, Angular and Vue for now, you can learn those when you grasp the basics.
Database is no different for web than it is for any other application, you can still use Entity Framework, basic ADO.NET or any other ORM you like.
Starting from the bottom is boring and probably way too easy for someone who is already a programmer.
Of course we all learn differently, but starting with <p>This is a paragraph</p> didn't work for me.
|
|
|
|
|
My daughter is currently doing web dev as a 1 year retraining course.
So far she has done...
- Pseudocode programming
- HTML5
- CSS
- SASS
- Bootstrap (IMO if you can get this to actually produce what you really want you're already qualified)
- Javascript
- WAMP/LAMP
- PHP
- MySQL/MariaDB
- Wordpress
- Shopify
I'll see if I can get hold of the complete syllabus if you're interested
So old that I did my first coding in octal via switches on a DEC PDP 8
|
|
|
|
|
Thanks, that looks like a nice progression.
Gives me a lot to look at.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
Choosing a tech stack is the hard part imo, but there are obv things every stack needs, and db is one, so learn it sooner. I much prefer sql to nosql, and recommend that you learn it as soon as possible. Find out how to read queries at a minimum because that will help you learn how to build them. No matter what CRUD libraries are available in your main engine language, you will need to understand how to build a query for what you want.
HTML shouldn't take more than a day to understand; after that, reference pages should get you through.
CSS can be as complex as you want it to be, and understanding how it works will be valuable even if you wind up using a preprocessor like sass.
JavaScript is fun and aggravating, but improving all the time, so you'll need to keep up if you are going to use it for more than drop-down menus.
Are you going to do web apps or native apps? That will tell you what JS framework to concentrate on if you're going to go that route.
|
|
|
|
|
Hey Max, just so you know, I'm saying this as a dude who's done a ton of web dev over the course of like 25 years. So, we're not talking about theory... it's about to get real. If I where to put things in order, I would suggest a path like this...
- Semantic HTML 5
- CSS Levels 2, 3 & 4 (including CSS animation... never animate in JavaScript unless it's on a canvas... never)
- Vanilla JavaScript (ECMAScript) (stay here a long while, do not rush it, learn to do everything natively that you would with a framework)
- TypeScript (a C# background will help; TS supports both the functional and OOP paradigms, do not rush this part)
- React (forget Angular or Vue React is king for now, this may change in the future though, do not rush this part)
- Node (forget ASP.NET Core for web dev, Node is king here for a reason)
- Npm (it may seem odd to mention this, but most folks don't know the majority of features npm supports)
- Database (100% agree to save this for last since most web devs don't know/do this anyway, but do learn both NoSQL and SQL, do not rush this part)
- Eventually learn WASM in Node and/or a language that will compile down to it. It's about to change the game dramatically.
Maximilien wrote: so I only need basic html and css. Respectfully, I'll have to disagree with this. I can count on one hand the number of frontend devs that actually know CSS. If you don't care about the user experience then just don't become a frontend dev. Seriously, why do you need a GUI if you don't want to learn how to make a good GUI? Yes, there are UI libs that handle most things for you if you don't want to learn and for a hobby that's ok. But, if you're looking to do this as a job, then set yourself apart and actually learn CSS.
Also, if you ever plan to do this as a job, semantic HTML becomes much more important when it comes to de-cluttering your documents and accessibility with screen readers, etc.
Maximilien wrote: I think I should probably do a good JavaScript course as it seems to be the big technology that everything else is based on (more or less). Yup, after HTML and CSS though. If you learn JavaScript first you may be tempted to learn stuff you can already do in CSS alone. If it can be done in CSS... do it. It'll always be the more performant route.
Also, be aware that JavaScript is insanely popular, and with that comes a lot of crap online written by people who have no idea what they are talking about. So, read everything, just be aware some things may have to be taken with a grain of salt.
This dude has a good JS blog and knows his stuff... 2ality – JavaScript and more.
If someone can't tell you the difference between a closure and composition... ignore every last thing they say about JavaScript. If they can't tell you about generators with a non-textbook, Googled answer... ignore every last thing they say about JavaScript. And so on.
Jeremy Falcon
|
|
|
|
|
Wooahhh!
thanks.
When I said, I need only basic html/css is that graphic design (page layout look and feel) is not my strong point.
I will revisit that.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
Forgot to mention, during the CSS part, you should also familiarize yourself with Sass with SCSS syntax. Despite the stupidity of politicizing their home page like the rest of the sheeple who don't think, Sass is a great pre-processor for stylesheets.
Jeremy Falcon
|
|
|
|
|
yeah, I've seen SASS popping up once or twice now.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|