I have done a lot of writing around front-end technologies in the past; for this particular post, I want to focus on Angular and why it’s the best choice for the enterprise environment. Before we get into that, I think we need to figure out what I mean by enterprise environment. When I think of an enterprise, I think of large teams, lots of contributions, and something akin to a slow-moving ship. In short, it’s a large company with a lot of moving parts and often quite a few different projects. There are many enterprise companies out there, and I…

I’ve talked about Agile before, but I think it’s time to talk about it again. I’ve worked in so many different Agile environments and have talked to other developers about their company’s Agile approach. Time and time again I see the same issues crop up and I wanted to talk about them.

Meetings, meetings, meetings

Welcome to part 2 of my Svelte journey! If you haven’t seen part 1 you can read that here:

Part 1 includes a brief history of Svelte as well as my initial feedback of what I think of Svelte after going through the tutorials and seeing some of the capabilities.

So I didn’t want to just go through the tutorial and call it a day. I really wanted to give Svelte a proper spin. So I decided I would make a basic to-do list application. You can find the code for it on GitHub here:

So right off the bat…

This week I decided to give Svelte a go and build an app. I wanted to answer a few questions, namely, what is it? What does it bring to the table? Should you consider it for your next project? I’ve never used Svelte before so this will be a learning experience for me as well. This will be part 1 in a 2 part series of my journey into learning Svelte. I wanted to do this all in 1 post but I feel like I have too much to write about and I’d rather break it up a bit.

A brief history


Sorry if I didn’t include your favorite front-end thingy

I’ve done quite a few posts now about Angular vs React and I’ve gotten quite a lot of feedback. So I wanted to take a quick step back and examine how do we pick what our front-end is going to be done in? With hundreds of choices in how to build a front-end how do we decide? Well, hopefully, I can shed some light on that and help you come to a decision in an impartial way.

If you’re looking for some simple definitive “use this always” kind of thing I’m sorry this ain't it. While I certainly have a…

Ok, so I wrote a post about why I felt React was a bad library and another one about why I thought Angular was better and you guys had some thoughts. So rather than try and go through and respond to all of you individually, even though I’d really like to, I’m just going to try and respond to common themes in your responses.

For reference here are the other 2 posts I’m referring to (in order):

  1. Why we need to stop using React
  2. Why We Should Throw Out React and Pick Up Angular

You don’t have to read them…

Ok, so I wrote a bit about why I think we should stop using React. To summarize the article a bit, there were several main issues I had with React:

  1. It’s mostly hype that drives its popularity.
  2. It gives you too much freedom, which leads you to make some really basic mistakes early on that sabotage you’re app later.
  3. It’s a memory hog and not tree-shakable.
  4. Your React app becomes exponentially more complex the larger it gets making it a hassle to maintain.
  5. There’s nothing built into it (like form handling) so you have to write a lot of complex…

Before we even get started I can already hear you pounding away at your keyboards writing your angry response. I would ask that you read my full explanation before going off at me in the comments. I really want to emphasize that I’m not trying to attack you personally because you use React or like React. However, what I am trying to say is that I think that React leaves a lot to be desired. What I want to do is explore the pain points and detail why I think React is an overall flawed library.

It’s mostly hype

In the business world…

Over the course of the pandemic lockdown working from home has become more widely available and very popular. However, we’re now reading plenty of accounts of broken work from home promises from numerous companies. However, I believe that working from home was going to be the future for most jobs regardless of a global pandemic. Today I’m going to give you my top 2reasons why working from home was and still is inevitable.

There was already an Increase in remote jobs

The first reason is quite simply this, there were already a growing number of work from home opportunities before COVID (at least in tech). I’ve written before…

For some background, I’ve been writing code since I was pretty young. I’ve always had a passion for writing code and solving problems and I’ve been in the field professionally going on for 6 years now. One part of the job I had never really gotten into was being an interviewer.

That all changed early on in 2020 when I started giving technical interviews. When I started out I had some ideas of what I wanted to do and how I wanted to be as an interviewer. I drew most of what I wanted to do from experiences I had…

Sam Redmond

Programmer with a passion

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store