Monday, 11 November 2019

Web Tutorial: The Contact Us Page (Part 1/4)

Contact Us pages are probably one of the most ubiquitous elements on any corporate website. It's usually the final item in the site map, or close to it, but no corporate website should ever be caught dead without it. That is the calling card of the site, and it incorporates contact details - phone number, mailing address, perhaps even a map - and a form for user feedback.

In this four-parter, we will be going through the process of creating one, from the ground up. This will be in PHP, so you'll need an appropriate server.

Why so long? It's just a Contact Us page!

Well yes, young buck, it is a Contact Us page, but it's not just a Contact Us page. When you have a submittable form, this opens you up to multiple forms of malicious attack. It's my responsibility to show you how to protect yourself against such, and go through other aspects of page creation such as responsive layout.

As such, this tutorial will be in four parts. First, we will make it work. Then we will validate input. After that, it will be about making it look nice, and layout issues.

We begin with some HTML.
<!DOCTYPE html>
<html>
    <head>
        <title>Contact Us</title>

        <style>
       
        </style>

        <script>

        </script>
    </head>

    <body>

    </body>
</html>


Now add a div and style it using the contentContainer CSS class. That's where all your markup will appear in, from now on.
<body>
    <div class="contactContainer">

    </div>
</body>


In it, add a div and its style will be messageContainer. Make sure it contains the PHP variable, message.
<body>
    <div class="contactContainer">
        <div class="messageContainer">
            <?php echo $message; ?>
        </div>
    </div>
</body>


Add another div, styled using innerContainer. The elements of your page will be in there.
<body>
    <div class="contactContainer">
        <div class="messageContainer">
            <?php echo $message; ?>
        </div>

        <div class="innerContainer">

        </div>
    </div>
</body>


In that div, we add three divs, styled using formContainer, cardContainer and mapContainer. For this part of the tutorial, we need only concern ourselves with the first div.
<div class="innerContainer">
    <div class="formContainer">

    </div>

    <div class="cardContainer">

    </div>

    <div class="mapContainer">

    </div>
</div>


In this div, we add a HTML form. The action attribute is left blank, which means it will submit to the current page, and the method is "POST".
<div class="formContainer">
    <form action="" method="POST">

    </form>
</div>


Now, add four divs within. Each of them will be styled using the CSS class formrow.
<div class="formContainer">
    <form action="" method="POST">
        <div class="formrow">

        </div>

        <div class="formrow">

        </div>

        <div class="formrow">

        </div>
       
        <div class="formrow">

        </div>
    </form>
</div>


We're going to ask for the user's name, email, and some comments. So add inputs and labels. Labels are important because they allow the input to be accessed by clicking (or tapping, in the case of mobile interfaces) on the label. On a large screen, it's not that useful, but if you were doing this on the small screen of a mobile phone, every little bit of extra usability helps. For comments, instead of a textbox, we use a textarea tag. Note that each element requires a name attribute. The name attribute is important for form submission. Also, we should specify the maxlength attribute to help prevent possible malicious input. 50 characters for a name and email, and 500 for comments, should be enough.

Also make sure the form elements all have id attributes - they'll enable the elements to be focused when clicking on the labels. Plus, they'll be useful in the next part of this tutorial when we want to get into the Document Object Model (DOM).
<div class="formContainer">
    <form action="" method="POST">
        <div class="formrow">
            <label for="txtName">Name</label><br />
            <input type="text" id="txtName" name="txtName" maxlength="50" />
        </div>

        <div class="formrow">
            <label for="txtEmail">Email</label><br />
            <input type="text" id="txtEmail" name="txtEmail" maxlength="50" />
        </div>

        <div class="formrow">
            <label for="txtComments">Comments</label><br />
            <textarea type="text" id="txtComments" name="txtComments" rows="5" maxlength="500" wrap="hard"></textarea>
        </div>
       
        <div class="formrow">

        </div>
    </form>
</div>


So your form is there. It's ugly as shit, but that's not an issue at the moment.


Let's improve on usability by adding placeholder attributes.
<div class="formContainer">
    <form action="" method="POST">
        <div class="formrow">
            <label for="txtName">Name</label><br />
            <input type="text" id="txtName" name="txtName" maxlength="50" placeholder="e.g, Jose D'Cruz" />
        </div>

        <div class="formrow">
            <label for="txtEmail">Email</label><br />
            <input type="text" id="txtEmail" name="txtEmail" maxlength="50" placeholder="e.g, j_dcruz208@youremail.com" />
        </div>

        <div class="formrow">
            <label for="txtComments">Comments</label><br />
            <textarea type="text" id="txtComments" name="txtComments" rows="5" maxlength="500" wrap="hard" placeholder="e.g, You're awesome!"></textarea>
        </div>
       
        <div class="formrow">

        </div>
    </form>
</div>


Yep, now we have example text to guide clueless users.


Add a button in the last div. The type attribute's value is "submit", which means it submits the form that it is in when clicked. Its name is btnSend, and this is going to be very relevant soon.
<div class="formContainer">
    <form action="" method="POST">
        <div class="formrow">
            <label for="txtName">Name</label><br />
            <input type="text" id="txtName" name="txtName" maxlength="50" placeholder="e.g, Jose D'Cruz" />
        </div>

        <div class="formrow">
            <label for="txtEmail">Email</label><br />
            <input type="text" id="txtEmail" name="txtEmail" maxlength="50" placeholder="e.g, j_dcruz208@youremail.com" />
        </div>

        <div class="formrow">
            <label for="txtComments">Comments</label><br />
            <textarea type="text" id="txtComments" name="txtComments" rows="5" maxlength="500" wrap="hard" placeholder="e.g, You're awesome!"></textarea>
        </div>
       
        <div class="formrow">
            <input type="submit" id="btnSend" name="btnSend" value="Send">
        </div>
    </form>
</div>


Your form should look like this now.


The HTML portion is done for now. Now we need some PHP code.
<?php

?>

<!DOCTYPE html>
<html>


These lines declare the variables message, form_name, form_email and form_comments, and sets them to an empty string. Also declare mailsent and set it to false.
<?php
$message = "";

$mailsent = false;

$form_email = "";
$form_name = "";
$form_comments = "";
?>


Next, we check for the presence of the POST variable btnSend by using the isset() function. If data has been posted to the page, the _POST associative array will hold the variables. And since we're checking specifically for a key named btnSend, this means that the page will not be acting as though stuff has been posted on every reload, only when there is a key named btnSend in the _POST associative array.
<?php
$message = "";

$mailsent = false;

$form_email = "";
$form_name = "";
$form_comments = "";

if (isset($_POST["btnSend"]))
{

}
?>


Here, we set form_name, form_email and form_comments to the appropriate values in the _POST associative array. These are all in the _POST associative array as key-value pairs when the form is submitted. We also run them through the trim() function to remove extra leading and trailing spaces.
<?php
$message = "";

$mailsent = false;

$form_email = "";
$form_name = "";
$form_comments = "";

if (isset($_POST["btnSend"]))
{
    $form_name = trim($_POST["txtName"]);
    $form_email = trim($_POST["txtEmail"]);
    $form_comments = trim($_POST["txtComments"]);
}
?>


Next, we call an emailer function. Using the name and email, we set the title and subject of the email, along with the headers. We'll use the n12br() function to convert the breaks in form_comments.
if (isset($_POST["btnSend"]))
{
    $form_name = trim($_POST["txtName"]);
    $form_email = trim($_POST["txtEmail"]);
    $form_comments = trim($_POST["txtComments"]);

    $headers = "MIME-Version: 1.0\r\n";
    $headers .= "Content-type:text/html;charset=UTF-8\r\n";
    $headers .= "From: " . $form_email . "\r\n";
    $headers .= "X-Mailer: PHP/" . phpversion();

    $subject = "Contact request from " . $form_name;
    $body = nl2br($form_comments);
}


Now, we'll use the mail() function and return the result to the variable mailsent. If successful, it'll return true and false otherwise.
if (isset($_POST["btnSend"]))
{
    $form_name = trim($_POST["txtName"]);
    $form_email = trim($_POST["txtEmail"]);
    $form_comments = trim($_POST["txtComments"]);

    $headers = "MIME-Version: 1.0\r\n";
    $headers .= "Content-type:text/html;charset=UTF-8\r\n";
    $headers .= "From: " . $form_email . "\r\n";
    $headers .= "X-Mailer: PHP/" . phpversion();

    $subject = "Contact request from " . $form_name;
    $body = nl2br($form_comments);

    $mailsent = mail("teochewthunder@gmail.com", $subject, $body, $headers);

    if ($mailsent)
    {

    }
    else
    {

    }
}


If successful, we want the message to be this.
if ($mailsent)
{
    $message = "Email sent. Thank you!";
}
else
{

}


If not, we use this instead.
if ($mailsent)
{
    $message = "Email sent. Thank you!";
}
else
{
    $message = "An error occured while trying to send your mail. Please try again.";
}


Note that the mail() function only serves to check if your values are valid. It could return true without actually sending any email. It all depends on how your PHP and SMTP servers are set up. My environmental setup is appropriate... but you might want to try some kind of external library for PHP Mailing otherwise.

Either way, let's test this input.


Success!




What if we modified this, an obviously invalid email?
$mailsent = mail("xxx", $subject, $body, $headers);

This is what you should get. If you don't get this, again, it could be your PHP and SMTP setup.


OK, stuff works. What next?

What's next is security. All we did was verify the presence of a btnSend variable. I could just as easily post variables to this page from another domain, and fool the script into thinking that it's valid by adding a btnSend key. So we'll add an Anti-CSRF Token here, as a hidden field next to the button. (It doesn't have to be next to the button; put it anywhere you want as long as it's within the form tag.) The hidden field will be named csrftoken. Its value will be the md5 value of the session id, obtained using the session_id() function.

Here's a previous web tutorial on the Anti-CSRF Token if you're interested.
<div class="formrow">
    <input type="submit" id="btnSend" name="btnSend" value="Send">
    <input type="hidden" id="csrftoken" name="csrftoken" value="<?php echo md5(session_id()); ?>">
</div>


Now, the session_id() function is useless if we don't start a session. So do this right at the start of the page.
<?php
session_start();

$message = "";


Then within the first If block, declare a variable, csrftoken. And if a similarly named key-value pair exists in the posted data, set csrftoken to this value.
<?php
session_start();

$message = "";

$mailsent = false;

$form_email = "";
$form_name = "";
$form_comments = "";

if (isset($_POST["btnSend"]))
{
    $csrftoken = (isset($_POST["csrftoken"]) ? $_POST["csrftoken"] : "");


Next, check for a match between csrftoken and the actual session id. It should be a match. Process the form only if there is a match. If it's not a match, someone is trying some Cross-Site Forgery on you, and you should change the variable message.
if (isset($_POST["btnSend"]))
{
    $csrftoken = (isset($_POST["csrftoken"]) ? $_POST["csrftoken"] : "");

    if ($csrftoken == md5(session_id()))
    {
        $form_name = trim($_POST["txtName"]);
        $form_email = trim($_POST["txtEmail"]);
        $form_comments = trim($_POST["txtComments"]);

        $headers = "MIME-Version: 1.0\r\n";
        $headers .= "Content-type:text/html;charset=UTF-8\r\n";
        $headers .= "From: " . $form_email . "\r\n";
        $headers .= "X-Mailer: PHP/" . phpversion();

        $subject = "Contact request from " . $form_name;
        $body = nl2br($form_comments);

        $mailsent = mail("teochewthunder@gmail.com", $subject, $body, $headers);

        if ($mailsent)
        {
            $message = "Email sent. Thank you!";
        }
        else
        {
            $message = "An error occured while trying to send your mail. Please try again.";
        }
}
else
{
    $message = "CSRF attack foiled!";
}


Try it! Change the value in the HTML to something else and click the Submit button.
<input type="hidden" id="csrftoken" name="csrftoken" value="<?php echo ""; ?>">


This is what you should get. Of course, the message will never show in the event of a real Cross-Site Forgery Request, but it's a good visual indicator of your security setup. Remember to revert the value of the hidden field after you're done testing.


Well done!

We've handled posting and handling form data. Your form works, and it's secured against CSRF. There's more to come, of course... stay tuned!

Next

Server and client-side validation.

Tuesday, 5 November 2019

An intolerance for the untalented?

Dinner-time conversations can take strange and introspective turns, and a recent one I had with a few friends exemplifies this well. Present were a couple friends including Jermyn, the dude from Macintosh Matrimony. We were talking about (surprise, surprise) - football. All (aside from me, that is) are fans of Manchester United Football Club.

Manchester United's recent dip in fortunes had us discussing old stalwarts like the fearsome Roy Keane, who wasn't as technically gifted as the footballers in Manchester United's squad today, but more than compensated for that through grit and passion, full-blooded aggression and the utter lack of sympathy for weakness. This led to a discussion of his success as a Manager, and how his brand of discipline was what some teams absolutely needed.

And then the topic veered towards retired footballers who are now Managers. I remarked that retired footballers don't often make great Managers, primarily because Managerial skills are very different from footballing skills (more on that another day... maybe). And Jermyn said that sometimes, the more gifted the footballer, the less patience he has with those who aren't as naturally talented. It was at that point one of the others said something to the effect of her understanding exactly what this means, because her boss often tells her to be more patient towards the mistakes of others as not everyone is as naturally talented as she is.

Ahead of the pack.

And that gave me some food for thought.

Not because I don't think my friends are talented. They probably are. I've never actually given the subject of their talent much thought.

And not because I don't agree that people who are talented don't have much patience with people who aren't as talented. From a certain angle, it does make a certain kind of sense.

But it did strike me that I exhibit a similar lack of patience with techs who make certain mistakes, and it's not because I think I'm more talented. Quite the reverse, actually.

You see, I don't think I'm very technically talented at all. There are concepts that I've yet to grasp, concepts that other techs seem to grasp almost intuitively. Everything I know, everything I've worked in, very little of it has anything to do with talent. It's all countless hours of trial and error, fueled by youthful (and now much less youthful) enthusiasm.

And it's precisely because of that, that I have very little patience for people who can't do as well. If I think I suck and someone does worse than me, there are only two possible conclusions I can draw.

The first conclusion is that if this person can't even be better than me, he's not worth bothering with. I don't expect tech talent to be great. I only expect them to be better than me. That's by no means a high bar.

The second conclusion is that this person can't be arsed, and that's a lot less forgivable. Code indentation, spacing, proper useful comments, testing your work - all these are basics. They're low-hanging fruit. You don't need to be a talented tech or possess some super-genius intellect to manage these. A child could do this. These mistakes are the kind of mistakes that arise from negligence, not incompetence. The latter I can forgive, because who am I to judge, right? But there is zero excuse for the former and I have very little tolerance for professionals who can't be bothered. Go do something else, because if you don't care enough about your work, someone else will. Being paid to code is a privilege that too few people actually try to earn.

I suspect that Roy Keane and I are very much on the same page in this regard. Talent can be trained. Attitude can't.

With much patience,
T___T

Friday, 1 November 2019

On Apple's decision to remove HKmap.live

The Hong Kong protests are still ongoing after more than fifteen weeks and these look to be harrowing times for the Pearl of the Orient. Amid all the hubbub, one fascinating aspect is how software tech ties into all this. Specifically, how web and mobile technology tie into it. That's a subject to dwell on another day - today I want to talk about something that happened weeks ago. The mobile app HKmap.live got pulled from the Apple App Store.

Now this by itself isn't that big a deal. Apps get uploaded and pulled all the time. The remarkable thing here are the circumstances around which this happened.

Apple pulled the app originally in early October, claiming that the app allowed users to evade law enforcement, and almost as quickly did the mobile app administration version of the Tokyo Drift, putting it back up and claiming it was a mistake. Then about a week later, Apple once again removed the app, and this time their CEO Tim Cook went online to provide an explanation.

"It is no secret that technology can be used for good or for ill. This case is no different. The app in question allowed for the crowdsourced reporting and mapping of police checkpoints, protest hotspots, and other information. On its own, this information is benign. However, over the past several days we received credible information, from the Hong Kong Cybersecurity and Technology Crime Bureau, as well as from users in Hong Kong, that the app was being used maliciously to target individual officers for violence and to victimize individuals and property where no police are present. This use put the app in violation of Hong Kong law. Similarly, widespread abuse clearly violates our ‌‌App Store‌‌ guidelines barring personal harm."

There have been voices from some quarters accusing Apple of not knowing right from wrong and allowing politics to interfere in tech. In principle, I agree. Tech should not be influenced by partisan politics. But here's the thing - while I don't like it, the world being what it is, I have to accept that this happens. To some degree or other, politics does have an effect on technology and how it is applied.

I don't think Apple was wrong to pull HKmap.live from their App Store. The only problem I have with their decision is them being so goddamn wishy-washy about it. Either allow the app or don't, but stick to your guns.

What is HKmap.live?

It's a mobile app that uses crowdsourced input from its users to provide a real-time report of police activity in Hong Kong, tracking movements of police officers. As one could imagine, such a utility would be of great help to the protestors. Unfortunately, it would also be of great help to attacks on the police force. There's been multiple reported incidents of police officers being targetted and assaulted, their families harassed. Whether the app actually has anything to do with this, as claimed by the Hong Kong Police, is yet to be proven. Yet, it doesn't take too much stretching of the imagination to see how this could be abused.



The app can still be run on the devices it is currently installed on and will still run on web browsers, though new downloads are no longer available. Even without HKmap.live, with other apps being able to perform pretty much the same function, it's unclear as though how much harm is actually being prevented by its omission from the App Store.

Why Apple was in the right

All tech providers are bound to obey the laws of the land, and if Hong Kong tells Apple that HKmap.live is in violation of their laws, endangers police officers and should be removed, Apple is obliged to acquiesce. That's not to say I think the pressure from Beijing didn't make an iota of difference; au contraire, I think it made all the difference in the world. But as far as I can see, Apple exercised their only feasible option, from both a legal and business point of view.

Why only HKmap.live, then? The question some laypeople are asking is, why only pull HKmap.live when other apps can do pretty much the same amount of damage? Why single HKmap.live out?

Well, the answer is pretty simple. It's a matter of manpower.

If Apple were to attempt to eradicate all apps in the App Store that could pose a danger to policemen, they would have to comb through the billion odd apps in there. Apple doesn't have time for that. They're too busy selling overpriced iPhones to their fanboys. The best they can do is respond to highlighted issues, investigate and react.

Messaging!

Wonder why messaging apps aren't pulled? They're a means of communication among the protestors, after all. (Telegram in particular seems pretty popular now). Because everyone knows that would be futile. Even if Apple removed all messaging apps from the App Store, what about games that have messaging functions? Where does it end?

That's the principle behind it. Respond to specific complaints, and do as little as possible. Apple isn't interested in protecting the lives of the Hong Kong Police. They're interested in staying on the right side of the law in the territories in which they operate. As they should be.

But what about freedom, democracy and stuff?

I'm definitely not a fan of China's heavy-handedness. From the NBA incident to PewDiePie, there have been numerous instances of China flexing their political muscle to silence and censor with regard to the ongoing spat with Hong Kong protestors. And as a Singaporean, I haven't forgotten the entire Terrex incident back in 2016 either. Make no mistake, China can be a right pain in the ass when she wants to be.

Not so peaceful.

I was happy to cheer these Hong Kong protestors on when all they were doing were peaceful marches. Months later, the protests are not so peaceful anymore. As a responsible adult, I am not going to encourage these guys to burn their city in the name of "Freedom and Universal Suffrage", all the while sitting there safely behind my computer screen. I'm not going to spout self-righteous bullshit like "some things are more important than wealth and stability" when it's not my wealth and stability that's under threat.

But let me just say this - Hong Kong is the city that these protestors live in. If they'd rather see it burn just to give China a black eye (and even then, how much of a black eye that would even be is up for debate), it's not for me to judge.

It's not my city they're burning. It's not my livelihood they're affecting and it's not my future they're claiming to fight for.

Similarly, these are not my country's policemen who are being targeted. If Hongkongers think that policemen getting assaulted and their families harassed is a small price to pay for change, that's their prerogative. But I certainly wouldn't recommend helping them to do it.


Peace,
T___T

Sunday, 6 October 2019

TeochewThunder: Year Five (Part 2/2)

It was a dismal year for readership, to tell the truth. I suspect this was in part largely due to the shutting down of Google Plus, which contributed maybe 10% of my usual hits. While the year started out reasonably well, readership went down after Chinese New Year, and hasn't picked up appreciably since.

Getting kinda lonely here, guys.

Luckily I'm not doing this for the attention, because that would suck.

Strangely, I think the quality of my work has gone up; though without readership stats to back up that assertion, it's an empty boast at best.

There were some things I could have written about. The year sure wasn't short on tech news. I could have written about Cloudflare and their decision to abandon 8Chan, the same way I wrote about a similar decision taken by their CEO Matthew Prince back in 2017. I even started ruminating over the new Code of Conduct at Linux and sabbatical of Linus Torvalds, before abandoning that train of thought altogether. The thing is, I'm sick to death of the USA and the never-ending online presence of their identity politics. Conservatives? Liberals? Fuck all of them. They should sort their shit out and I'm certainly not giving them any more air-time than I need to. My little pieces on Patreon and Twitter earlier this year was as far as I cared to go.

Sure, writing about stuff like that attracts the attention of even non-techies. But I shouldn't lose sight of what this blog is for.

The biggest hit of 2019...

One blogpost stood out among all the others when I did some investigation - the two-parter Women Can Code, Get Used To It! This had the second biggest number of hits in the entire history of TeochewThunder, almost matching the current record-holder, 2018's Ten Principles of Adult Learning Applied to Software Development. I suspect a huge part of its popularity was because I shared this with several female friends, not all of whom are from technical disciplines, and they pretty much did the rest by re-sharing.

Gorgeous geek girls?

Interestingly, the second part of Women Can Code, Get Used To It! was far more popular than the first. I guess people were more interested in my declaration that tech is not a gender-specific profession, rather than what I felt was more interesting - examples of pretty ladies that don't conform to the geek girl stereotype.

On further review

It appears that a web tutorial from 2017 has suddenly gotten a lot of attention - way more attention than I think it deserves. It was basically a BMI Calculator written in AngularJS, and the first ever AngularJS tutorial on this blog. Again, yes, don't look a gift horse in the mouth... but damn if it isn't suspicious.

Future Plans

The road map for this blog features a lot more reviews that I never had time to write - books, apps and my ongoing writeups about the TV series Silicon Valley, which, sadly, looks about to end its run soon.

I'm also trying to keep to the basics, because I've always been all about the basics. There's a lot to cover. Fun or boring, they all have a place on this blog. 2020 looks promising. There's so much to write about, and the list looks to be growing all the time.

Thunderously,
T___T

Thursday, 3 October 2019

TeochewThunder: Year Five (Part 1/2)

This October marks the fifth year since TeochewThunder was started, and what a journey it has been so far. There's been plenty to write about, and I'm not running out of material anytime soon. Although there have been times I just didn't feel like writing. Blogging is an exercise in discipline. It forces me to keep exploring; keep my eyes, ears and mind open for more related topics, and most importantly, it keeps me honing my craft. It's a veritable ocean out there and I'm a shark; if I ever stop, that's it for me.

Can't stop!


Still, compared to hectic madness that was 2018, this year was a breeze. Being married and all, I can't devote as much time to this enterprise as I'm used to, but sometimes it's all about time management.

It also gives me a sense of purpose. Because work can drive me nuts... and when I get home, I need something to remind myself that I still love this shit. Something fun. Something productive.

Tutorials

2019 is the year I return to my roots - instantly browser-executable HTML, CSS and JavaScript, but with additional front-end niceties like jQuery UI, AngularJS and ReactJS thrown in. My style of coding has changed slightly. I'm now particular about spacing and indentation (fine, more particular than before) and when I do get the chance, my preferred style skews towards Object-oriented Programming. Happily, I still find time to do a little PHP, Ruby and QBasic.

Nothing really significant has changed otherwise; I'm still the nerd who codes outside of office hours and derives more pleasure than is reasonable from it. This results in at least one web tutorial a month, and I plan to maintain that standard.

Reviews

There have been a lot of reviews in TeochewThunder this year. Almost every month, there's been a review of some sort or other, and happily, they have been somewhat evenly spread out between film, app and fiction reviews. Reviews are easy to write, usually, and I've discovered a newfound enthusiasm for it. Also, many of these are backdated. While I collect the screenshots and all, I don't always have time to write all these reviews.

This blog is about more than tech reviews! And I have to be careful not to turn this into a review blog.

Miscellaneous Features

Spot The Bug. I manage about three of these a year, and to this day, I have not broken that streak.

Ropework analogies. One a year seems reasonable. Again, I've managed to keep that up, though this year's seemed a little trite. No matter, all part of the journey.

Listicles. These are fun to make; however they're also a lot of work. They used to be a good way to group related ideas into one blogpost so I wouldn't have to overlap too much when discussing similar ideas next time.

Work on teochewthunder dot com

Things have gotten a wee bit more expensive since 2018, what with me paying for hosting. Still, considering the benefits that this resource brings me, it's a small price to pay.

I get a domain name and a portfolio for prospective employers. It isn't great, but it's a heck of a lot better than nothing, which incidentally is what many developers have other than a resume and a lot of bravado. I don't really understand why other web devs don't invest in a domain name and hosting, especially when they're technically more skilled than I am and have a lot more to showcase. But it works in my favor and you know what they say about looking a gift horse in the mouth.

And it has worked. I attended interviews this year and the interviewers all mentioned the amount of code I've put online, along with my tech blogging. Sure, they don't always say it's good, but still. It's a body of work that has spanned years and it's being noticed by the audience for which it was intended.

All in all...

I sometimes struggle with not writing too much, especially when I have points that I want to make. But part of effective writing is restraint, and it's something that many people, not just me, could use more of.

Cutting away all that fat.


Every overly wordy Social Media post or article I come across annoys the living beejeezus out of me and I try very hard not to fall into that trap. These days, more time is spent trimming the fat than actually writing.

Next

Check out some of the stats on this blog!