Posts
This is All the old stuff, will keep it for inspiration and history sake.
Trending now
12 - New features and fixing bug for HTML5 MMO Scripters War
Computer Advanced Custom
21d) - Computer Advanced Custom. This is going to be the last general computer knowledge …
How to learn web development Article from CodeWeb
I was Just reading this article. It is Spectactular and very well written. There is no r…
13 Expert-Level Blog Design Tips for Beginner Bloggers from incomediary
The hits are comming one after another. 13 Expert-Level Blog Design Tips for Begin…
Another Test
Testing Permalinks This is the Host Provided From
This Section will eventually be the Portfolio section. Until then it will host the details of the ongoing big project.
ReplyDeleteProject name: Journey to a full-stack (from full nada).
Overview: It is an education log, containing all the details, steps and material used to learn about Web Development. Full-Stack from full nada, what does it all mean exactly? Please allow me to explain it properly:
Full Nada: This is the starting point, my skills in this are mostly in computer hardware repairs. As for software, mostly on how to use them, no clue in the makings. And in the web development department, Nada, Nicht, not a single clue. Lies, I know that webpages are built with HTML, not what it means or is, just the initials. Typing in 2 fingers, and not having written much since my last education. Unless post-it count, or digital notes.
Journey: Doing a switch of a career is always a big change. Due to certain life-difficulties, and some future problems that need to be dealt with. I need to have a work from home, while able to work remotely, meaning that, I have to be able to provide income for my family, while the location to be irrelevant. Flexible, and upon though becoming a Web Developer came to be my solution. And so, This project became a reality. This is the journey in plain words, now the way to approach it and actually make it through is where this actually differs.
Methodology: Learn, write, evaluate, record, proceed. This is it, upon research I've created a curriculum in the skills in need to be learned. After picking and studying a subject, I will write a small article. review, essay about it, effectively doing too many in the process. By writing we can perfect the knowledge about the subject, also getting a better writing flow as well.
End Result: Having the valued skills of evaluation and self-assessment and a better-written word. A meticulously recorded and detailed C/V, down to the last concept. A live portfolio showcasing a timeline of improvements. A blog with social media coverage and a community of people. A guide written from personal experiences and remarks. And most importantly a job as a-
-Full Stack: developer. From full nada to full-stack, long way? short way? at the end of the day, it is a "way".
Blog and review/article writing, Web Developer
ReplyDeleteMy name is Alexander, I am from Greece and i welcome you all to my personal Blogspace.
Entry-level web developer and article/review writer. An inquisitive mind, patient, good communication skills. Determination and driven by strong personal reasons. Flexible availability all day, night and day. Current occupation night club manager. C/v with multiple varieties of careers, highlights of many years of service in Michelin star restaurants, Inside Athens and in islands over summer full occupational Work hours. Able to work many hours per day, week. Able to devote off time Towards honing career skills, able to take schedules Maintaining a blog and a GitHub repository as an ongoing project. Striving to be a Full-stack developer and make a life project from it. Here you will find all my details and contact info spread through the web.
Social Contacts:
Personal Facebook
Facebook Page
Twitter
Instagram
Pinterest
Flipboard
Other Profiles:
Patreon
Medium
Other Ongoing Projects:
Bookmarks
Roadmap
Professional Details:
Linkedin
Upwork
Online C/V
Community:
Github Repo
Quora
Stack Overflow
This section will hold all reviews that don't actually fit into the Web developer section.
ReplyDelete1) - Viral blog writing 101 by Wolken Navarro.
How To Write a Better Blog Post.
Viral blog writing 101 by Wolken Navarro.
Blogging, Blog post Writing, viral.
Welcome! According to today's schedule, it is a blog day. And this course was the best option for a beginner's class. So without further ado, let us proceed to the overview.
It begins with a very basic and short part about how your blog should be structured precisely. Moving on from general blog strategy to post writing strategy. Covering everything from the headline picking to grammar checking tools. There is even a part that covers the angles on post writing. Simple, detailed and not very long as well, about 73 minutes.
And as I mentioned before this lesson is around 1 hour and 13 minutes. Not very long considering the output of info it has. Very detailed and he also has a very clear voice which makes the lesson so much better. On to the actual thing now. After the introduction video, there are some basic blog structure rules. The category of your blog, subcategory's and topics. Closing in with a few tips on how to pick an angle, for writing your post. Followed by a template, and to be honest that was a very good idea, and explanation's for each part. First up is the headline name picking and some suggestions, cause the actual headline strategies are explained more detailed in the ending videos. The new pickup was: SEO - Search Engine Optimization, which is used by search engines to find keywords and makes your post more easily discoverable. Again, more about that in later courses. Onwards to the introduction of the post, an anecdote or a short story. Or a Nutgraph, meaning a Post in a nutshell paragraph. To a transition line that makes getting into the main body of the post more smooth. This is followed by a few supporting key points to solidify your post. The closing section is an epilogue with a punchline, or as Wolken tells it, a CTA, a Call To Action line. A short punchy and powerful sentence to entangle your readers. Down the line is all about having a flow in your writing and sticking to the point. Finally, there are some tips on how to clean and perfect your post, and also the tools for proofreading.
All in all, is very engaging while viewing it, I had ideas hitting me all over the place. Also, a template and structured writing came out of it. Very recommended and many thanks to Wolken Navarro for making this course.
1) - https://guides.github.com/activities/hello-world/ #1 - Git - Starter
ReplyDeleteFirst guide on git. The very manual, learned to created repositories, pull, merge and edit changes. I can call it the very basic training of git, the barebones. More than 10 minutes needless to say. I took my time and ended up in half an hour's worth of course. That's me guess. Also to note that the guide is based on website control, no command line support. Also the first Article. Well.
2) - https://stackoverflow.com/questions/315911/git-for-beginners-the-definitive-practical-guide
#1 - Git - Advanced.
The second guide, a google result, it turned out to be practical as advertised. But the order is a bit weird, I went from configuring the git to searching terms I had no clue what they were. Well, all in all, it is rich and content friendly. It is not for me at this point, so I will keep it around as a reference and for random questions. Well as of now, I have visited this guide many times, I have added that it helped me a great many times. Not only the guide itself but also the comments, you canfind plenty of resources, answering to some more inquisitive minds.
3) - https://guide.freecodecamp.org/git #3 - Git - Starter. 2# - Vscode - Starter
Now, this is what I call entry-level, the most useful guide so far. I can feel the entry-level now, we got some basic concepts and 101s. Git is a distributed control system that helps multiple users or coders have access to a file or program (hosted online on repositories) and modify it. Plain? Simple? Yes but not so much. What shines is in the inner workings, and in this git-case, the impeccable history, and logging, containing date, time changes and comments. Imagine 100 people proofreading the same page at the same time, in different places. After they are done they send the pages to the author to review and accept or refuse the changes. This is git, takes all pages, compares the changes, checks the reasons for the changes, merges the changes with the original page, and voila 1 page merged with 100+ corrections. Ending in a clandestine document passed by 100 sets of eyes, and also a history behind it, all the changes that it went through from the original state, along with the reasons for the edit, the date/hour and the author of the changes. All that in real-time, connecting all of the worlds. Clone - Modify - Stage - commit - push. Five words are all I have.
4) - https://code.visualstudio.com/docs/editor/versioncontrol #3 Basic after some VScode Tut.
This was one more step up, inside the basics always. We delved inside the VSCode, the text editor of choice, more on that later, there are over 6 lessons to be covered here. Some basic integration is not bad to know. So all in all our editor of choice has all the functions already, just some configurations. The new introduction was the extensions inside the editor, more as we go there. For the time being, "Github Pull requests" the extension, it allows you to process and accept pull requests from within our IDE. Also now we see, in the status bar below the text editor, the username we have inside GitHub. another new tool to have around is the Azure DevOps. Another online host of personal repositories, which connects perfectly with your GitHub account, and your Microsoft account. vscode + Github + Azure DevOps. before the question "why another one like GitHub?", I think it will have its uses. We will keep it around and see in time. Could be a Gem in the long run, or a powerful portable solution, time will tell. I wish I had some training in VScode, waiting for another chair, my house, and my multi-monitor setup.
5) - https://www.freecodecamp.org/news/the-beginners-guide-to-git-github/ #4 Basics Done.
ReplyDeleteWell, useful but I could not follow it via the correct order. Around half of the guide, the instructions tell you to add a sample.html. All cool, but the surprise came when you actually have to create it first, inside the local repo directory. Yeah, welcome to the frustration, the newbie got stymied. After a good day searching the most creative key words ever, I asked in the QA community. Namely Stack Overflow, a specialized central to ask anything programming-wise. There are communities about every subject inside Stack Exchange, the mother site of QaAs. Wanna ask something about something? Go there, the first choice. So after a question, some edits, some more searching, I was tinkering inside bash and an error came up. Searching about it, came to answer my own question and solve all my problems with git and that bash. Ending my frustration and the tutorial. Coding is all about experimenting, asking, problem-solving, and using communities. So I have a feeling that today we did all of that. Mission accomplished and some extra, "https://github.com/firstcontributions/first-contributions". This little gem provided us with the umpf we needed, and also supplemented this course lovely. Pulling a repo, accepting an issue and solving it, pushing and getting a pull request, waiting for the acceptance of edits, and thus making the first active contribution ever. I would say at this point that we have completed the basics, with git, and that we now need more specialized knowledge, more on skillset.
6) - https://www.joelonsoftware.com/2003/10/08/the-absolute-minimum-every-software-developer-absolutely-
positively-must-know-about-unicode-and-character-sets-no-excuses/
Well a rather funky tutorial, has a taste of humor that might not appeal to everyone. I don't know if there is a bare minimum in anything, and I don't know what the heck encodings is. But Joel says he can rectify that, and trust me he does. It had some techniques inside i can't say, but skipping past the terms and a bit math, I got it. How from ASCII we went to the Oem and later to Unicode. Speaking of which Unicode was the attempt to unify all codes. All letters in Unicode are assigned to an id, named code point. Eventually, all words are a set of code points. Now on to encoding, first, the Byte Order Mark, which adds an EF or FF to the code point, telling you if it's up in the memory or low. Also, UTF-8 with 1-byte storage on 8 bytes. UTF-7, UCS-4 and plenty. After reaching the end of Joel's guide, we know what encoding is, how to use it and how to effectively debug encoding errors. Also a reference to the Unicode map. Id dare says that Bare Minimums are achieved. And a highly recomended one, its excellent.
7) - https://www.w3.org/International/questions/qa-what-is-encoding
8) - https://www.w3.org/International/getting-started/characters
9) - https://www.w3.org/International/tutorials/tutorial-char-enc/
* H1) - https://ohshitgit.com <-- Honorable Mention 1
ReplyDeleteAnd there we got to, perhaps and not only, the best eye-candy of an article/tutorial that i could ever lay eyes on to read. Yes I am talking about all those situations where all that frustration i had with git, commands, console, integrations, migraines with VSCode, were layed to rest. My own slice of heaven, reference to season 4 Rick n Morty, personal pooping place! Not only the article maintains a keen sense of humour that pleases even the hardest costumers, but it also provides you with a cheat sheet of the commands that will save you from an OH SHIT?! GIT! Situation. Also examples, ways to use them and a peace of git you will never forget. Read it, Highly recommended as well and also a excellent bookmark, kudos you get to name it.
13) - Basic Format & Structure of a Readme.
ReplyDeleteWelcome back, this is the first side lesson, it is about the readmes. Apparently, and not without reason, readmes have standards. Makes sense but I did not know about it. Easy lesson, probably about half an hour or so, clear and builds up real fast. First about the readmes, then about layout and after that how to represent it. Then moved to knowledge-wikis, how to build and construct them properly (markdown) and some more extra info related to the next review. All in all it is not exactly a lesson, more like some guidelines, guidelines on the bare minimums of readmes. I consider it more like standards of the internet, or as Joel might have said it "The absolute bare minimums every developer should now about Readmes". Good conduct, read it, learn what a readme me is, the reason for existence, etc. You know, I have some years on me, some years of home computer repairs going around folks places and repairing or making changes to personal computers. The reason I am telling you this, is cause due to this when a readme is on my way it gets tossed instantly. That did change after that. It is now my firm believe, that readmes are a very important part of any project. Please add it to the requirements. Licenses as well, more on that on another article. Next is Markdown.
14) - Markdown - Basics #1
15) - Markdown - Advanced #3
16) - Markdown - Basics #2
17) - Markdown - Basics #3
18) - Markdown - Basics #4
19) - Markdown - Advanced #1
20) - Markdown - Advanced #2
These are 7 sources used to learn the basics of markdown, and some more special like creating lists with multiple check boxes in a horizontal line. I know how to do them vertically, but the horizontal was a problem. Lets analyze them properly, one by one mind you, the order might not be perfect. Until the curriculum is updated and I can make some sense of it. IF you are following me in this, until my system is perfected, please bear with me, this is trial and error. Also please contact me via any means of social, i would love to have a discussion and some fresh ideas, approaches etc. Now let us begin.
14) - Markdown - Basics #1
ReplyDeleteAlrighty first one we are gonna cover is the basics of markdown. If you notice some similarities with HTML, it is cause they are in fact almost the same, HTML and Markdown are part of same genre of languages, Markup. The way I understood it is, that you mark specific words or text, with special tags. And the text takes the properties of the tag. Ether that is to hide the link into a disguise text, add an image, make lists, or quoting text. Different from HTML not in how it is handling the text but more actually in the commands used to mark your text. Here an example:
```
HTML bold tag text
Markdown bold tag **text**
```
Different commands, Different types or dialects of a language, same results. Now let me explain it properly, is it a method of text formatting for having structured documents. Website = Text Document with structure and a formation, a way of presenting organized information. Time to move on, four links in the bottom of the site and the first from the top is our pick.
15) - Markdown - Advanced #3
This is the first link and it is just my luck to be a wee bit advanced. How so? Because here we are into GFM, Git Flavored Markdown, a dialect of markdown. Meaning it has a base of Markdown, hence and the name of course, and some customized commands used to make communicating with GitHub. And so this is a lesson taken later after some more markdown done. That been said let us proceed to the the actual lesson. We will be switching the terminology for starters cause it's wrong. Commands are as I call them is the syntax and the semantics of the language. Semantics are for a rather extensive review, cause it is a category on its own, having semantics for everything, it seemed to me that it is very important, in so it will be covered on it's own separate category of skills. Now back to the lesson at hand. Personally I went through it and it was very difficult to understand it. So forth make a note of it. We will use it again in future reference, as of now it is not needed atm. Learning actual HTML is more important. We need some basics, in order to get started. After that it is all a matter of getting into the Git more seriously. We can use git to learn languages as well, so it is a win win, like typing is constantly improved.
16) - Markdown - Basics #1
This link is really small, based and focused more in the graphical interface of the website. Yeap we are talking about the website, doesn't need any syntax. It is the most simple way to format your text. Press a button and the magic happens. Simple and effective. It shows and explains to you, what every button in the ribbon does. In case we bored, well not much else going on here let us move on to the next one.
uch. This one lets you know that there are automatic methods of link shortening, and auto link reference. What does that mean exactly, means that you can write for example: #26 and it is the same as https://github/jlord/sheetsee.js/issues/26, yeah, well it is life saving. Truth is I can't quite make out all of it, but as we said before the important bits. We need just as much info as possible but not the heavy things.
ReplyDelete18) - Markdown - Basics #4
This is your bread and butter right there, bookmark this and save it under a cheat sheet folder or something. This is a list that contains the most basic syntax. It is light to read as well, read it a couple of times and practice the syntax, as you type markdown you will be using this list quite often, until not. This is the same with mostly everything we will learn so cheat sheets are the way to go for the long run.
19) - Markdown - Advanced #1
20) - Markdown - Advanced #2
Again this is for reference as well, I was in the need of checklists, and this was my answer. As for the second link, I've decided to include it as an extra. How to create a vertical multi check box inside a line. And that was it, this covers in extend the basic markdown we need, some advanced bits and some extras. Also a reference card, well to be honest these are small reads, not really an review each, so consider this to be a big review broken down in sections. Next up is Licenses, how, what, whys, and what to avoid. Have a nice night.
ReplyDelete