Is it even worth becoming a “web professional” now and what does that even mean?
It can be strange how we categorize our positions and professions. For example, what one person would call a web developer, another would call a web designer. Then there are web programmers and specialties like “front end”, “full stack”, “back end” and “mid-thigh carver” ( I made that last one up, and yes, the last place I came from was the butcher’s…). So then what is a web professional?
And there are other questions, like is web development going to be obsolete with products like WEBFLOW and the like (products that will take away the need to code)?
With these titles and questions swirling around it can be very easy to throw up your hands and say what am I doing?! Is this even worth my time?!
The answer is: yes, yes it is and as far as ‘what is a web professional?’, well, that is a little more complicated…
First off, shameless plug: We offer kick-ass, detailed, and laboriously designed courses that will help to answer this question. So a web professional is kind of all these things combined in different ratios: designer, developer, front end, full stack, braised tenderloin ( I think I’m getting hungry…), etc, etc. Some devs may specialize in specific things (ex: back end or client side whatever), but it’s all in there. Hodge-podge is not necessarily the right word, but it’s the first word that comes to mind…
And how do you, as a web professional, ensure you know all these things or have a passable knowledge/experience with them? You learn. Either from having “been around the block” or by taking our course <another shameless plug, I know!>… But seriously, web development or whatever you want to call yourself is not going anywhere, in fact if the rate at which things are becoming more and more technological keeps growing, we’re going to need more and more devs at all kinds of different strengths and experiences.
Check out the vlog for a way more detailed and in depth explanation of this subject and quick side dig at RUBY… -Enjoy!
HTML4 classic formatting tags, vs modern HTML5 interpretation of semantic tags.
HEADS UP: We’re answering what may be considered a beginner’s question so if you’re super busy and you already know the answer to this, feel free to move on. But there’s a little nerd history lesson in it…
So, “what is the difference between strong vs. bold tags, and between EM(emphasized) vs. italic tags? To me, they look the same on a web page. What is the purpose of distinguishing between the two?”
Great question. Simple answer: it’s semantics NOW… “You can use either/or today; it doesn’t make a difference.”
Historically: “when HTML was first invented there was no CSS, so they needed tags (a set of html tags), to allow web pages builders to add some styling to the page. ie: add italics, make certain texts bold, insert images, etc. So the early browser-makers … created a set of tags that were display tags: they allowed to change the look of things on the pages.”
As things evolved and HTML5 came along, the powers that be decided to give semantic meaning to the tags instead of having programmers go back and update/correct their previous work. Now, that being said there is absolute use in these semantic tags; for example those with accessibility issues like the seeing impaired will have a “reader” talk the page out and in that case, the reader will interpret paragraph tags, heading/footer tags,etc and it may become pretty useful.
Another use would be to target a very special audience or for very specific web application needs…but that’s another video…
Speaking of videos, please check this one out for a more in-depth history lesson with way more charisma than the typed word.
Also -shameless plug- Our web development course teaches you the infrastructure / history of these tags and how they operate. We like to go above and beyond -Check it out. Plus at the end of the video, some sweet summer heat and beach!! Enjoy!
WordPress, is the most popular CMS in the world … and for good reason.
Spoiler Alert: Yes, WordPress did approach us to do this.
Also, SPOILER ALERT: we don’t know how to use spoiler alerts…
It’s not selling out or corporate schilling because we actually believe in and love this product, and are happy to tell you guys about it. It works for us and we hope it works for you, if you need something like this; plain and simple. Yes there are other platforms comparable to WordPress and if you are happy with them, more power to you. But if, you’re curious about it, we think you’ll find what you’re looking for, whether it be style or function.
We could list all the amazing functions and plug-ins right here but it’s easier to just watch the vlog.
That way you can see my awesome sweater-jacket too 🙂
These days, UX and UI are by far the most important aspect of any web app and perhaps, most software written. At least any software that has a visual component.
Let’s get down to it! For those of you on the fence about becoming programmers and are reading this and breathing a little shallow because you have no idea what we’re talking about, “and oh my god, I can’t do this, I don’t know anything…” Breathe, my friend… You are welcome here and all is revealed to those who ask…
UX = User experience. Essentially how a client/customer “experiences” a website. IE: are the articles too bunched up that it hurts the eyes? Are all the buttons the same color? Is the “BUY NOW” button right under the product so you can see it and not have to go looking for it? Etc.
UI = User interface. What the user interacts with to “experience” your product. IE: Touch screens, laptops, phones, etc
I’m not going to lie, these things do overlap sometimes and the blurred lines can make even the most seasoned programmer start muttering curses under their breath, like Yosemite Sam. But instead of separating the two, let’s lean into it. Let’s look at a set of principles that will make all your work in UX (with a dash of UI) streamlined, simple and elegant…
I really recommend watching the video for further explanation because, “there’s a certain set of rules but there’s also a bit of an art to it. …I’m going to teach you some of the rules that I’ve learned over the last few years in terms of designing UX for user interfaces whether it be websites web apps or mobile apps…” …and also I want you to watch the video. Enjoy!
PS – As always, stick around after the chat for a soothing ride that ends up…in a cemetery!!! I know, right?!
These days we have many options when it comes to building websites, but which is the best way to build in 2018?
Let’s talk websites and the building thereof… So, you’re a small business owner or an aspiring website creator? Maybe you’re just interested in what goes into building a website. Well, there are many options and each has their PROs & CONs:
HTML & CSS The traditional way to do web design coding, these would be the two “languages” you’d have to learn and they can (theoretically) build any type of website. “There is literally no limitations, in terms of what you could build if you got into the nuts & bolts: the basics of building a website.” However, the downside is that you’re going to have to learn it; that is to say time investment, theory, practice; all the stuff that goes into learning a skill. But that being said, you know how to program!
Web Design Programs These can range from programs where you have to know a little bit of code (Dreamweaver, Brackets, etc.) to content management systems (CMS) like WordPress, down to easy site builders like WIX, for example. All are very different approaches (which we will touch on in the video) and vary in the amount of control you will likely have…
The key word here is control. As we go from straight up coding down the line, we lose flexibility and versatility; it goes from creating the very thing you see in your mind’s eye, to “what you see is what you get” on the building sites. And of course, that’s fine too. There’s nothing wrong or lazy with building a “wham-bam” website if that’s what fills your needs, but check out our video and you might get an idea of how to better fill those needs. And check out the links at the bottom if you’re curious about the aforementioned web design languages. Mastering the code of website creation does have it’s perks…
Do Web Developers need to Promise Web Sales for Clients?
So you’ve got a client; maybe they’re your first, so you really want to do a good job and WOW them. Maybe they’re not but you’re a professional and always putting your best foot forward. But these clients are asking/demanding something that you’ve never really had to deal with before. They want you to prove the efficacy of your work. They want a tangible return on investment. Maybe you want this job so bad that you decide offer a guarantee that few others in your field can offer…
Can you/should you offer web sales?
Short answer: No. Why would you? That’s not really your job. General rule of thumb: “If you have to convince a business that a website is good for their business, then you probably should move on to another business.” “It’s like convincing a business that having a telephone is going to be good for business, so that the client can call them”. In short it a little crazy, bordering on unreasonable and not you responsibility.
On The Other Hand…
If you’re positive you can deliver on this promise (maybe you’ve even negotiated a tidy 25% of the sales generated from the website on top of your fee), then provided things go smoothly, Cha-Ching! But, would you be about to watch this video if you were 100% sure things were going to go smoothly? All sorts of problems can arise from you not being an expert in the client’s; not knowing what drives sales or their model, to your client booting you and you having no recourse, just to name a few…
We’re gonna look at some of the challenges facing web sales for clients and throw a few tips and strategies your way. And just in case you’re feeling a little anxious by all of this, stick around to the end of the vid where we’ve got a nice little view and a moment of serenity to keep things in perspective. For some of you already in the middle of a bad client web sales drama, take a breather.
Are you being original or just gumming up the works?
A simple -if not a little insulting- acronym. How many times have we come across a co-worker, a manager, or even a boss drooping the old “kiss bomb”. Keep it simple, stupid… easier said than done? Sometimes, YES: absolutely. But other times, when we take a step back and look at the whole picture (maybe even take our egos out of the equation), we come to realize that simplicity can be clean, elegant and best of all easy.
Huge messes of code are a symptom of one or more of the following:
1. bad developers
2. overly complex frameworks
3. coders purposely hiding code …. by making it insanely complex.
At the risk of sounding old, “It’s not cool to write complex cryptic code that nobody can understand. Simple code is the best code”…ya young punks! And really you’re only hurting yourselves… What’s gonna happen when you have to go in 6, 8, 10 months down the road for updates and you have no idea what’s going on?
The pros keep the their work simple and clean where they can and not only do they look good, competent and in control; it saves them time. So get out there make life simple for yourself.
To begin with, look to design principles:
– font use
– color use
If you have your page elements nicely lined up, don’t use more than two fonts on the page(!), keep your page colors properly matched (no clashing colors) and give the page a lot of breathing room (good use of whitespace) … that will go a long of making the website look good.