The face of native mobile development is changing indeed … and fast!
Okay, so a couple of months ago we talked about SWIFT and how we felt it was going to “lose market share” because frameworks like FLUTTER, React, etc. were going to put more pressure on native development (like SWIFT) with their sheer versatility… it did not go over well with the SWIFT OG’s… but if we could just have a moment of your time, I’m sure we can make things worse… 🙂
“Flutter allows you to write cross-platform mobile applications (iOS & Android) using one language: DART, one framework: FLUTTER framework, and it’s created by google; and what interesting about FLUTTER -it compiles down to native so you don’t have a ‘performance hit'”.
Now, traditionally when you use frameworks, you don’t have access to certain things that you would with native but the major concern when creating FLUTTER was to give developers the ability to customize and have access to everything…in other words: flexibility. Writing and maintaining one code base which is responsive, compiles down to native is gives you a lot of control over UX and UI is pretty attractive and while no framework is perfect, it’s pretty close…
In the video we go into more detail and hit on a few interesting points. Check it out, it’s worth a look. Enjoy!
Any experienced developer will tell you that soft skills makes the difference, if you want to move up in the ranks … maybe become a tech lead, or software architect.
Our culture used to idolize the cowboy. That loner who does things his own way and to hell with the consequences. He doesn’t say much unless he’s telling people what’s what, and rides off into the sunset with everyone all the better for having come into contact with him…
And what did we used to say about anyone who didn’t automatically strike out as a tough guy? Anyone who used words and diplomacy? We’d say they were “emotionally intelligent”; that they has a set of “soft skills”… oddly patronizing, no?
Well, the truth is that the “cowboy” is a blowhard that can’t work well in the group, and “the group” is the better way to get things done. Talking to people, working with them and making them feel their opinion/input matters. That’s how you build relationships (business or otherwise) that will last.
Check out the video, it expertly touches on what we’ve hinted at, but it’s pretty much what you’d expect:
“…being self aware both emotionally and intelligently.” Knowing your strengths and weakness (and being confident or humble about them accordingly). In other words, “Know where you suck” and also “realize where you’re good too”. In the end “being self-aware like this, both emotionally and intellectually is a very good thing to be; it’s good to be in that state of mind…it’ll have a tremendous positive impact in your life.” Enjoy!
Alright we’re going to lightly touch on this and if there’s enough of a public outcry, we’ll gladly do a deep dive but for now let’s skim over client side Vs. server side rendering. YAY!!
Now, full disclosure: It’s better to watch the video than to spend time reading what’s being written. The video is quick articulate and makes good and knowledgeable arguments for sides better than writing this out. But if you still feel like reading on, here’s the (very) skinny…
CLIENT SIDE RENDERING: So when you’re looking at the app/website, the views you render/send out (to the web browser) for the client to see. Generally you want to keep the views pretty simple when it comes to the processing power behind it.
The downside? Not everyone has the same hardware on their computers and may encounter trouble viewing the page (ex: web browsers not up to date, lag, slow load times, etc.)
SERVER SIDE: Does not rely on your viewers having the most up to date web-browser or fastest computer but it does require a lot of server side processing power…
So what’s a dev to do?
Check out our video for answers and opinions. Enjoy!
In a word …Nah… “I don’t think there’s ever going to be an official CSS4 specification…in terms of how CSS is developed…they now release CSS in terms of being module, so components of new CSS comes out…and are widely excepted by all the browser manufacturers.”
But before you go grabbing all the new and shiny things, we do have a warning for you as an active web professional/developer: just because you see a certain technology or feature is implemented in the specifications, it doesn’t mean that you can use it. “It takes awhile for browser manufacturers… to put into place these new capabilities according to the specification.”
And the kicker? Even if these browser manufacturers do streamline these capabilities into the newest versions of their product, not every person, business, or entity will not be using that browser, they’ll be suing an older browser and not even an the updated version of it. “A lot of people do not upgrade their browsers on a regular basis; some don’t upgrade them for years! So depending on your target market, …you may not be able to implement a particular feature that very modern browsers implement.” I know, it’s frustrating, right!?
So in conclusion, there’s not gonna be an official CSS4, there will be new CSS capabilities released into the ecosystem, but shinier is not always better.
Check out the video for a more robust explanation by a human (me) and <shameless plug>: we do offer a CSS course where we teach the foundations do you really get the sense of how it works. Also, for our followers out there or people interested, we go into how we chose which features to implement when we designed webstudio and the thinking that went behind it. Enjoy!
PS – We were just having a little bit of fun with words in the headline…we love you, CSS
Coder burnout is more common than you think and everyone loses motivation once in a while…
First let’s talk about burnout.
Sadly, it happens. Does this sound familiar? You’re focusing so hard on either the work or the theory that goes into the work. You live it; you breathe it! You are the fountain of knowledge from which all inspiration for the project flows forth and then…mayday, mayday!! Crash and burn<out>. All of a sudden you need to take 3 months to a year off because you either have nothing left to give or the very thought of the work gives you the shakes… Good news is you’re not alone, we’ve been there and here’s a tip:
Unplug: For serious. Go outside, go to the gym (check out our previous vids about working out and staying fit…). A change of scenery will always help, even a good meal ( like, one you cook, if you can.) can help calm, nourish and refocus your energy. The work will always be there when you get back. And with your brain re-energized and calm, it can refocus you can reap the benefits. Honestly, even taking a walk to go grab a coffee has been shown to hit the brakes on stress and refocus that narrow vision…
Now, about motivation…
It’s totally normal. We are all human beings and every now and then we lose interest and lack motivation. Something else enters our field of vision and we deem it important and tend to push everything else to the side. Sometimes we even leave the tech space and take a hiatus only to comeback (years) later. What can we do about that?
Take it Slow: You can’t expect to come back in your first day “and be firing on all cylinders”. Especially if you’ve been out of the game for awhile, there might be some new things to learn and that’s okay. The good news is for the most part, things haven’t changed (for example you still have front end/back end), perhaps the way you used to think about the tech space will have to change but some or most of the process remain…
Check out or video for a more in-depth talk about this subject and be good to yourself. Take time and relax when you can; it’s a good habit to get into and you’re gonna need it eventually… 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!
A basic business lesson…be very careful about who and what binding business relationships you establish.
The general idea I want to get across is: don’t get into unnecessary deals with third party companies. Really think hard about what the “partner” brings to the table for you to want to “partner up” with them.
Now, specifically I want to talk about…
MCN: multi-channel network: A company that claims to help “grow” your channel (YouTube, in this case…), by taking control of your channel for x number of years, where generally all the income is funneled to the MCN, and after the “number of years” the income is returned, minus the MCN’s cut and generally you have no idea what the MCN has done, did or was planning on doing or the “help” they provided was ambiguous, uncertain or (in your best Unicorn voice), highly dubious. In my opinion it’s predatory. Also, see rent-seekers.
Generally the stuff they offer is stuff that sounds like you need their help getting but when you think about it, you don’t. Example: free access for using stock footage (you can get that yourself for about 20$ a month which is way less than their fee).
In the video we’ll link to some YouTube content creators that got hosed real bad (if you haven’t already heard) as an example. Plus some of the experiences we had in the past. Enjoy!
Hard to learn, easy to write … but slow to code with
ALSO: It’s dog-slow at run time when writing desktop applications (never mind mobile apps).
So there you have it, from a guy that loves JAVA. It’s super verbose and heavily detailed in the writing (which also means less errors because you’re being explicit), and that writing code takes much more time, much more time means much more work and money/cost: “I wouldn’t do it.”
Check out the video for a more in-depth explanation PLUS what’s coming up with us with STUDIOWEB and other fundamental stuff we’re working on; super exciting stuff!
Soooo, long story short: I went to California for a business/pleasure trip. I was staying with family and while they were out, I entered their property and tripped the alarm (they hadn’t given me the code). I called the “fam”, got the code, entered, made a coffee and chilled out.
Now, what happened next, you gotta click the video and listen to believe: it’s pretty amazing…depending on your level of comfort with guns (that’s right plural), raised voices, and the police in general. Now I want to preface this by saying that everything is fine, and I don’t fault the officers that were simply following protocol, but the lesson here is to stay calm and move slowly…always…and no matter how many guns you have pointed at your face…(yeah, seriously!!). Check out the vid and Enjoy!
Which programming languages will be the most popular in 2-3 years from now? Should you even care?
Since the dawn of time, man has looked up to the sky and wondered what the future will bring…
Where will we live?
Will Pokemon revolt and catch US for their own twisted means?
…And what will the programming languages of the future be?
Well we’re not gonna sit here and cook something up, my crystal ball is gathering dust in the closet and I’m only going to bring it out when it attains “vintage” status, so I can sell it for a killing on craigslist…
But, by market share PHP is the biggest. It’s got to the point [where] “…none of these languages are going to go away any time soon, simply because they’ve reached that tipping point where they’re woven into the nerd language.”
It’s really the same thing with all the BIG languages. They’re part of the background and still very much a part of the forefront. They are relatively easy to use, convent and almost universally understood by virtually all of the developer community (even though opinions on them will differ wildly…)
Thinking about it from a practical standpoint, with the corporations you work(ed) for, let alone huge multi-nationals regarding the languages they use in their products: “…they’ve all gotten so good now that there’s no real major reason to want to change from one technology platform to another… for some company to want to move off PHP to PYTHON there has to be something really compelling about PYTHON or something really bad about PHP.”
Check out our video, where we explain our “theory” and drop some hints about what we think the future will ultimately bring…plus catch the (backhanded) nod to RUBY (we should be keeping track of these…). Enjoy!