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.

Messages - Gary-SC

Pages: [1] 2
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?

What a fantastic way to start the new year. Today was the first day of work at my intern job, and I had a "heated discussion" with my boss. The culprit? Tailwind CSS Framework.

My boss said that we were about to start working on a UI of a new website that one of our clients would build. He wants me to use Tailwind CSS to create a few basic templates. Take a look at this bullcrap nonsense here:

This dumbbutt framework is littered with class names for every freakin' element. All of them are for "writing CSS without writing CSS" because, according to my boss, the backend engineers don't like writing CSS, and it will supposedly help them work with various customization later on.

I got so angry at this bullcrap nonsense that I launched a full presentation right on the spot to SHOW him why it did not make sense to use it. I ended up receiving more of the same nonsense replies like, "You need to be humble and willing to learn different tech stacks," "You are a beginner, so you can't have a 'balanced view' until you do what we tell you," "You need to be more pragmatic than that," etc. etc.

I think I'm going to quit. I'm done with this "Oh, you are so beginner that you can't say we are wrong" bullcrap. Honestly, I think they are bullying me at this point because I talk back to them.  >:(

I've known about the state of the industry, but I still didn't expect it to be as bad as I have now seen. I understood it in my head, but I didn't experience it at this level, and it's shocking to me.

My company does so many things that I consider utterly unnecessary. They use Wordpress for a site that would be easier and more secure to use a static website. They use Bootstrap CSS, which I have seen NO evidence that it is easier and faster than writing a decent HTML/CSS without it to accomplish the layouts that are simple to code in pure CSS. Stuff like that. And, I haven't been able to find anyone at my intern job who would understand half of my observation. It makes me feel like I'm just joining a pack of criminals committing blatant fraud.

I did send my boss to this site a while ago, by the way. He thinks that there are many good ideas but also thinks it's "too idealistic" to practice in the context of working with a team. He also said that things were different now that people were doing stuff like CSS-in-JS, generating a dynamic page in React.js, and so on. He said that the Bootstrap framework helped his team to be on the same page because it's well-documented, and it's just easier to be able to add classes in HTML to make it render the way they want. I contended it was another proprietary layer of rules we had to learn on top of pure CSS. Why not just stick to pure CSS standards? His answer: "You haven't worked with a team. You will get it when you are ready to do that." Sigh. Can't argue with people like that.

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 / Re: Mac or PC?
« on: 29 Nov 2019, 08:47:46 pm »
Interesting. People are quite split on this subject.

My verdict for myself, at least for now, after talking to a bunch of people and reading/watching reviews and reports: I'm going to keep using my old MBP and not spend money at all until it actually dies. Besides the battery getting old, I've actually enjoyed using it. It still does what I need it to do without any hassles and slowdowns. The keyboard issue hasn't affected me personally since mine isn't that keyboard. A few friends who own and use PCs or both all have mixed/different opinions about it as well, but they all pretty much told me just to use whichever I happen to have. I'll take that, since it seems like everyone has different opinions and preferences, and no sides seem significantly rosier than the others overall. A bunch of pros and cons and potential problems. What I have at the moment is working for now, so I'm okay with leaving at that and not buy anything until I know what I want.

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 / Re: CSS selector order: what is the best practice?
« on: 19 Nov 2019, 07:25:11 pm »
Thank you for your insights. It makes sense. I will try that idea for my next job.  8)

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?

Introductions / Re: Hello
« on: 28 Oct 2019, 03:33:48 am »
Thing is, the way he took to it once the concepts were explained, Gary reminds me so much of Dan Schulz. A year or two he'll make me look like a rank amateur, come back and start teaching me stuff.

No way!  :P The more I learn, the more I realize how much I do NOT know. I love learning this stuff, and I hope to get better every day. But, I now realize that it might end up being life-long learning.

I am HORRIFIED to look at my posts at Digital Point Forums now, but I'm glad I posted them because they show me that I am making at least some progress in my understanding. I feel like a different person, to be honest.

The unfortunate side effect, though, is that I get angry more often because I realize more and more that there is just so much highway robbery going on out there. Even after a few months of being exposed to all kinds of craziness by my first "mentor" at my other job and some of the forum posters advocating against good work ethics, I am still appalled whenever I see someone selling a web design service for $2,000+, and all he does is to pick a pre-made template (often Bootcrap), "customize" it (a.k.a. changing a few parameters) and calling it a "custom job." I've even seen it done at my current intern job. And not to mention "SEO service" one of their clients got from some marketing agency earlier this month. I was asked to get involved, so I got to see how they did their stuff. I saw the invoice, and it was somewhere around $7,000, and all they were doing was mainly a bunch of fiddling with a few customized Bootcrap templates for what they called "a/b testing" and fiddling with Google Search Console.

But, I digress. :p

Introductions / Re: Hello
« on: 28 Oct 2019, 03:12:18 am »
Hi Gary, it is surprising how easy it is to get tangled up in this coding malarky, especially with all the rubbish information available at the click of a button.

...And, I get a lot of rubbish advice even from some of the devs at my intern job. Just the other day, it went like this:

Sr. dev: "We are going to use Bootstrap for our new site template."

Me: "Why not write it from scratch? I can do that so you won't have to, and it's faster for me to do it than using Bootstrap. Besides, Bootstrap is bloated, and it encourages bad practices, and..."

Sr. dev: "I appreciate your enthusiasm, and I agree with you. But, our devs need a standardized CSS library to make it easier to work with various templates across the site."

Me: "A simple in-house style guide should do the trick if you must have one. But, I can write simple stuff, and I don't even think you need it."

Sr. dev: "Well, again, it's hard to maintain stuff when it's not standardized and documented well."

Me: "...??? What do you mean? I don't write anything outside the standard HTML/CSS."

Sr. dev: "Well, I appreciate your input, but this is what we are going to do as a team. As an intern, I think it will be good for you as a learning assignment. You know the basics. You'll do just fine with Bootstrap. You don't always need to do custom stuff."

Me: "......." (sigh)

They sometimes leave me with a massive confusion as a result of this type of illogical "persuasion." CutCodeDown is one place where things make sense. 

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] 2