Minimalist Semantic Markup

Welcome Guest
Please Login or Register

If you have registered but not recieved your activation e-mail in a reasonable amount of time, please use our Contact Form for assistance. Include both your username and the e-mail you tried to register with.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Gary-SC

Pages: [1]
JavaScript / Is JavaScript eating HTML!?
« on: 20 Feb 2020, 02:43:20 am »
Not sure what to think about this article. I'm skeptical of the whole concept because I either don't see any point in doing this, or I'm utterly ignorant of the subject and have a lot more to learn to appreciate what this article is discussing. Any thoughts/counter-points, anyone?

It's been a few months since I started working as an intern for a web dev agency. The more I work for them, the more I find myself depressed, even though I love doing this stuff even more. I love coding stuff, but I hate how everyone is about pragmatism and compromise.

I say Bootstrap and Sass are both hassles, and I want to code without them. My coworkers say I am *still* a beginner, and I just haven't learned all the good things about them. "Good things?" Like, how they create more work to write HTML and CSS? That Bootstrap is the modern-day HTML3 inline style approach? As a lowly intern, I've worked with hundreds of pages of Bootcrap pages they assigned me to edit by now. I keep telling myself, "I could code this page much leaner without Bootcrap," but it's "just what it is," and I "just need to work with it," according to my boss. This "who cares, it's what everyone needs to do" attitude is the default, and I'm growing quite weary of it.

Perhaps I am just too caught up in my coding ideology? I'm disgusted and lost.

PC Hardware / Mac or PC?
« on: 28 Nov 2019, 07:32:41 pm »
I am currently on a seven-year-old MacBook Pro that someone sold me cheap to do all my general computing and web development stuff. It's still working fine with an SSD installed, but its battery runs out of its juice in less than two hours, even under a light load. It also disconnects my Bluetooth mouse that came with it when I bought it from him regularly.

In light of all of that, I'm looking into buying a new laptop. I am wondering whether I should take this opportunity to migrate to Windows laptop, or I should get a new MacBook Air or Pro and run Windows via Parallels Desktop for testing with IE. My needs include anything related to web development, being able to do all the things I'm going to learn for web development (ex. local server, testing environment, etc.) on top of all the usual general computing stuff. I have zero interest in playing computer games, but I want to be able to have some fun editing photos and videos. I want to be able to run several tools without a loud fan running all the time, and I want my battery to last for 4~6 hours if possible, not just two hours or less.

I like the idea of MacBook Pro running multiple OSs in some way because it sounds to me like it's the best of both worlds. But, I've heard that the "Butterfly Keyboard" on MacBooks for the past four years has been awful for so many people. I heard that Apple refused to acknowledge the problem until this year. Looking at the specs out there, it also seems to me like I could get more for the bucks with Windows laptops. But then, I've also heard that developers prefer the Mac because it's UNIX-based while also have access to all the familiar software people use. But THEN, I've heard of Windows 10 has a way to do UNIX-ish stuff besides MS-DOS prompt.

What do you guys recommend? Which laptop would you buy? I have already saved up and budgeted $2,600 cash. I am willing to invest since it's what I will use heavily every day. However, I do not wish to spend any more than I need if, for example, $700 laptop will do all the things I described above more than sufficiently. I am not a cheapskate, but I don't want to spend "just because."

Other Web Programming / GUI shaming?
« on: 21 Nov 2019, 08:34:01 pm »
I was reading about Git the other day and came across this article somehow. It talks about how developers shouldn't shame people for using GUI tools to work with Git:

Do you think his stance on this matter has some merits, or do you think it is another case of "wah wah i dunn wunna learn!" nonsense?

My impression is that it is the latter, but in general, I am a bit biased toward being cautious of tools as a result of having seen a lot of bad ones for HTML/CSS. I learned to use Git via CLI at my intern job, and I don't find it particularly challenging in terms of doing basic routine tasks. But, some devs at work have mentioned that they sometimes liked using it for diff and visualizing branch flows. I don't know, I just can't imagine Linus Torvalds using a GUI client, so I tend to think competent programmers would not use one, either. I also feel like learning to use CLI and automating things helps me to learn how it works and to reduce tool dependency. I prefer to use my cheatsheet plain text file to look up and memorize basic commands instead of having to rely on GUI tools for it. Am I being too gun-ho about this stuff, or am I on the right track in taking that approach? Thoughts and suggestions?

HTML / CSS / CSS selector order: what is the best practice?
« on: 18 Nov 2019, 02:57:46 am »
I have been wondering about this article which I came across a while ago:

What is the best practice for ordering CSS selectors? What do you suggest?  In general, I've been following this article's advice; going from global to more specifics.

I can't help thinking to myself, "Maybe they just need to learn more instead of relying on yet another helper tool." Shouldn't we be fluent in HTML/CSS to be able to spell out at least the most essential and commonly used tags and attributes correctly?

SEO and Content Creation / General SEO tips?
« on: 26 Oct 2019, 03:50:01 am »
I'm trying to learn SEO basics. Here is my outline so far. Am I getting it right?

- Most of it is about making good content. Write for users, not for search engines, and write something of value.

- Write correct, semantic HTML. Focus on proper handling of h1, h2, h3, etc. and <hr>.

- Write proper meta description and meta keywords.

- Make your site fast and accessible.

- Create XML sitemap.

- Use HTTPS.

Question: Should I include the "structured data" information? I am not entirely sure whether it is absolutely necessary.



Introductions / Hello
« on: 25 Oct 2019, 09:54:49 pm »

I'm looking forward to learning more. In Digital Point Forum, Jason rescued me from all kinds of misinformation. I'm still relatively new to web development, but I've already discovered that the "highway robbery approach" to web development is unbelievably common.  >:( It makes me angry! CutCodeDown has been my go-to reference when it comes to HTML/CSS, minimalist semantic markup, and even how to think in general.  :)

Pages: [1]