<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jesse O&#39;Brien on Medium]]></title>
        <description><![CDATA[Stories by Jesse O&#39;Brien on Medium]]></description>
        <link>https://medium.com/@jesse-obrien?source=rss-2ea626b1b810------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*DlASzg0jQo-5pRIx.jpeg</url>
            <title>Stories by Jesse O&amp;#39;Brien on Medium</title>
            <link>https://medium.com/@jesse-obrien?source=rss-2ea626b1b810------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:19:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jesse-obrien/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why Not Discord For Business?]]></title>
            <link>https://jesse-obrien.medium.com/why-not-discord-for-business-a32abc84c693?source=rss-2ea626b1b810------2</link>
            <guid isPermaLink="false">https://medium.com/p/a32abc84c693</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[technews]]></category>
            <category><![CDATA[discord]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Jesse O'Brien]]></dc:creator>
            <pubDate>Thu, 22 Apr 2021 00:13:05 GMT</pubDate>
            <atom:updated>2021-04-22T00:13:05.770Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*X60YJNSu9WW4NkpJ" /><figcaption>Discord’s Logo. Cute innit?</figcaption></figure><p><em>Discord has the potential to create a business offering that could rocket their valuation into the tens of billions and knock Slack out of the #1 spot.</em></p><p>Some (subjectively) good news happened this week with a company I love. <a href="https://techcrunch.com/2021/04/20/discord-ipo-microsoft-deal">Discord will not be selling to Microsoft</a> and will instead look towards IPO. It makes me happy knowing that Discord will continue on down their path and manifest their own destiny, avoiding the gargantuan pull of Microsoft’s gravity. Now, I’m not inherently <em>anti-</em>Microsoft. The last few years of their commitment and investment in open source has shown us that they’re taking it seriously. In my opinion, though, converging too many paths under one umbrella is bad for consumers.</p><p>Anyway, that’s not what this article is about. Their IPO decision got me thinking about something I started mulling over early last year when <em>almost</em> <em>everyone who could, </em>started working remotely. Discord has the ability to do something I don’t think any other chat app has done. Discord server’s build a sense of <strong>community.</strong></p><h3><strong>Work. As A Community.</strong></h3><p>Fundamentally what <em>feels</em> good about going into an office is the sense of community. Being social, hearing some gossip, knowing your co-workers better than just their day-to-day accomplishments, bumping into someone and having an off the cuff conversation to toss ideas around.</p><p>This is what I’ve heard time and time again from everyone that’s reminiscing about what it was like going into <em>the office.</em><strong> </strong>They miss being social. This is what feels so broken right now with Slack, Microsoft Teams, Twist and the handful of others in the market. Slack doesn’t <em>feel</em> social. It feels sterile. It feels like email. The way it functions is almost anti-community.</p><h3>It’s Broken. Here’s How to Fix It.</h3><p><strong>Slack and Teams operate on a hidden-first communication basis</strong>. Every interaction is done from an <em>individual</em> standpoint. An individual invites others to a <em>private chat</em>, an individual can call another individual, or start a call with multiple folks, but they need to be selective about who. There’s no such thing as an <em>open door</em> on Slack, other than channels. However, even channels are based on individual interaction. Channels are hidden by default and require the <em>individual</em> to seek them out. Alternatively, a lot of people just learn about them through word of mouth. Everyone’s had the “oh, we have a #pets channel for that!” experience at this point. Great. I’ve been here for two months and didn’t realise I’m not in the crowd of people who had the idea to create a channel for #whatever-thing and I wouldn’t have found it unless I mentioned my interest.</p><p>At best, this self-discovery works mildly okay for those who are ambitious enough to want to jump into more community feels with something like Slack. At worst, in my opinion, it contributes to massive breakdowns of communication across teams and alienates individuals from each-other and their companies. Loads of companies are promoting transparency as a value they hold dear and yet their Slack text communications are about as transparent as a brick wall. The text itself is great for transparency, the way Slack intrinsically forces users to hide their text with each-other, is not. People get used to their regular DMs. They get used to their regular channels. They get used to silo communication at every turn, because the pathway to trying to make things open door is almost non existent. How many of us want yet another group chat with random individuals polluting our Slack sidebars? #general or #announcements gets too noisy, then what? Where do we put those things? These questions are being asked at thousands of companies around the world right now <em>and there’s no good answers</em>.</p><p><strong>Discord operates on a community-first communication basis.</strong> Every channel is visible in the sidebar as soon as you join. Text chat is there, but <strong>so is voice and video</strong>. Discord has the ability to create user groups, give users roles, hide channels with per-channel permissions, but by default it expects you to actively pick what you might want to hide. It can emulate Slack’s insidious hidden behaviours, but you need to opt into it. You need to choose what to hide from the folks that will be in your community. It’s not going to assume private by default.</p><p>As an individual who’s probably new to the company, I land in a place where I can see what’s available to me and jump in as I see fit. There’s open voice channels sitting there just waiting for me to join them. I can look across the landscape of the company culture immediately. Beyond the business-centric channels that I’ll use for daily communication, is there a #memes channel? What about #stonks? or #running, #linux, #baking, #parenting, #outdoors?<em> I get a quick sense of where I might fit, and if this place fits me back.</em></p><blockquote><strong>If you wish to take something private, you’ll need to actively break out of the community-first interface that Discord forces on you.</strong></blockquote><h3>Voice.</h3><p>Voice channels. Nothing beats em. I can see who’s in the voice channel and quickly pop in to see if they want company. By the channel name, I can probably judge what I could do without thinking over it too much. If the channel name they’re in might is <em>#watercooler </em>I know I can just drop in to chat. I can relax and maybe meet someone new, catch up on what people have been doing. With a channel named #exec-meetingsI’ll probably leave it alone unless I’ve been invited to an executive meeting. It’s possible that #exec-meetings is private and I don’t have access, but that I can also see when things are happening there. No different than being in the office.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/231/1*WkSCfGRXZB6hdylfGmmdFw.png" /><figcaption>Voice channels!</figcaption></figure><p>There’s no time restriction on voice channels either. Channels are <em>always open</em>. It’s not someone’s private zoom room that will disappear if they leave. There’s no host juggling. It’s the same as an open room in a building. It’s opt-in, but it’s very clearly there. No different than the conversation in the lunch room in the office. There’s no requirement for video either, even though it supports it. You can just hop in with your microphone and start gabbing.</p><h3><strong>Video.</strong></h3><p><em>Zoom fatigue</em> is setting in deeply by this point in most of us. The endless blocks of time booked into our calendars just draining the hours away. The way video calling works in Zoom and Slack sucks. I don’t like it. It’s a massive context switch to another program. Slack’s video window pops over the existing Slack chat window and I need to tab around to find it again, yuck.</p><p>I think Discord’s voice &amp; video channels (broadcasting as well) present a better way. They don’t rip you into a separate context, they just present you with new information in the same context. When you join a voice channel with participants that have video enabled, or they’re sharing their screen, you can open up that view by just clicking the channel name. Need to answer something in a text channel? Click it, it’s right there. Video is, again, a feature that’s right at your fingertips of you want it, but it’s a much more subtle focus of the program versus the Zoom/Slack interface.</p><h3>Quality of Life.</h3><p>Discord has a host of things that are great quality of life items. It gives individuals very granular control on how they experience the app and others. The ability to choose to mute others voice and video. Tired of seeing people? Disable their video. Someone’s mic too quiet? Bump their volume. Add notes to people. Mute a channel straight away.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/188/1*Ax3INkI3tHqzi_Z3QhnTQw.png" /><figcaption>Discord’s options when right clicking a user.</figcaption></figure><p>The invite system works very well compared to Slacks convoluted signup process. This might be something Discord won’t be able to escape when approaching single-sign-on for the business world, but I’d imagine they’d find a nicer way to implement that loop as well.</p><p><strong>Here’s a few features I think would be killer for Discord.</strong></p><ul><li><strong>Implement meeting rooms.</strong> Include the ability to knock on a voice channel to see if you could hop into the meeting, imagine how nice that would be?</li><li><strong>Send a quick voice message to someone.</strong> Allow users to send a voice message with an invite attached to join a voice channel. Not much different than yelling across the office. “Hey, do you have a sec to help us with thing you know about?”</li><li><strong>Have a bulletin board channel type. </strong>Folks can post pictures or events on a feed. It’s not meant to be engaging, it’s meant to get the word out about stuff going on at the company/department. Have one for each department. That way, you can “walk past” their bulletin board and see what they’re up to.</li></ul><h3><strong>Changing What “Business” Means.</strong></h3><p>Most folks I’ve talked to about this idea have said the same thing. Discord is was built for gaming. What I think many businesses are missing is the fact that communicating in games is just as important as it is at work. Sometimes more important. Not often during any average day running a business do you need instantly clear, concise communication that could mean the life or death of your business. Gaming often requires exceptional communication to bring players together to win epic battles, coordinate detailed mission details at specific timed intervals and the ability to be clearly heard while in high intensity situations. Discord owns that. They’ve done incredibly well at it. They’ve built their platform upon solving the communication problems gamers have been having online for over two decades now.</p><p>I’ll offer an interesting anecdote. When I played in a Guild (a group of players that organise themselves like a company) in World of Warcraft, that guild was much better organised and communicated better than companies I’ve worked for professionally. We were focused on goals. Organised dates and times where we all had jobs to do and deadlines to meet (Bosses can spawn at specific times). We put in the work to ensure we were prepared as individuals and also executed reliably on teams of players. Tell me again how gaming is so much different from business? Instead of updating JIRA tickets or excel sheets to complete a project, a player might be harvesting materials and mining ores for potions or equipment that their guild-mates need to complete a goal. My point is, I think a lot of businesses could benefit from seeing how great self-organising gaming communities run.</p><p>One valid critique I’ve come across, which I agree with, is the sense of security around video sharing sensitive business meetings or content with Discord. To that, I would say that Discord just needs to have a think about what a community-minded security model could look like. No different than the feature above, have the ability to give users different levels of clearance. Maybe restrict video sharing on certain channels at certain times and have the ability to unlock it by request. Who knows? There’s a huge hole in the market right now that’s making work less fun for everyone. I think Discord could fundamentally change what “work” and “business” means for all of us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a32abc84c693" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Brief History of Laravel]]></title>
            <link>https://medium.com/vehikl-news/a-brief-history-of-laravel-5d55970885bc?source=rss-2ea626b1b810------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d55970885bc</guid>
            <category><![CDATA[history]]></category>
            <category><![CDATA[laracon]]></category>
            <category><![CDATA[php]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[laravel]]></category>
            <dc:creator><![CDATA[Jesse O'Brien]]></dc:creator>
            <pubDate>Mon, 18 Jul 2016 14:16:30 GMT</pubDate>
            <atom:updated>2016-07-18T14:22:23.587Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jm3JQ3oEElHfTdNzPjGnLA.png" /></figure><p>At Vehikl, we use the Laravel PHP framework in most of our web application development. We’ve long been a part of the Laravel and open source communities, actively contributing to both by authoring packages, volunteering time, and supporting conferences.</p><h3>Once Upon a Time…</h3><p>Up until about 4 years ago, the PHP community was a wasteland of competing frameworks. Conferences were a mass of framework creators talking about what they were working on and what their framework did best, engaging in boasting matches over whose framework was the best solution to a problem.</p><p>Today the community is far more cohesive and collaborative, and Laravel has evolved within that movement.</p><h3>The Laravel Vision</h3><p>Taylor Otwell, a .net developer in Arkansas, was using CodeIgniter when the first seeds of Laravel were planted.. “I couldn’t add all the features I wanted,” he says, “without mangling the internal code of the framework.” He wanted something leaner, more simple, and more flexible.</p><p>Those desires, coupled with Taylor’s .net background, spawned the framework that would become Laravel.</p><p>Traditionally, PHP had been like the wild west of programming languages. Because it is dynamically typed, there are a lot of things that could potentially go wrong with no warning. For example, in other languages, code is written in such a way that if a mistake is made it can be caught before code execution .Either by trying to use the code or by compiling it, the compiler would actually stop you, identify the problem in the code, and require you to fix it before moving forward.</p><p>Out of the box, PHP has none of that. So theoretically you can continue writing poor code without knowing whether or not it works, forever. When something does go wrong, you have to spend a lot of time hunting for the problem.</p><p>Taylor aimed to solve all of those problems with Laravel. He used the ideas of the .net infrastructure, which <a href="https://www.microsoft.com/en-ca/">Microsoft</a> has built and spent hundreds of millions of dollars of research on.</p><p>With Laravel, Taylor sought to create a framework that would be known for its simplicity. He added to that simplicity an expressive syntax, clear structure, and incredibly thorough documentation. With that, Laravel was born.</p><h3>The Laravel Infrastructure</h3><p>He started with a simple routing layer, a really simple controller-type interface (model, view, controller or MVC); v1 and v2 were released in June 2011 and September 2011, respectively, just months apart. Laravel 3 came just over a year later, in February 2012, and this is when Laravel’s user base and popularity really began to grow.</p><p>In May 2013, Laravel 4 was released as a complete rewrite of the framework, incorporated a package manager called <a href="http://www.jamfsoftware.com/products/composer/">Composer</a>. Composer is an application-level package manager for PHP that allowed people to collaborate instead of compete.</p><p>Before Composer, there was no way to take two separate packages and use different pieces of those packages together to create a single solution. First you’d have to download the files, put them into a certain spot, figure out how to use them, and blah, blah, blah.</p><p>Composer became the tipping point where suddenly all of these framework authors starting looking at one another and started to see the benefits of collaboration instead of competition, and Laravel began to make a real impact in the PHP world. Today, we’re using Laravel 5.2, with Taylor continuing to make improvements and innovations to the framework.</p><h3>Lassoing in the Cowboys (and Girls)</h3><p>As word spread, a lot of people who were doing the whole wild west PHP thing started to pay attention to Laravel. People started to appreciate that Laravel was very structured, the syntax was nice, it was expressive, and the components were named well. Taylor’s aim has been to build a framework that can take the most unskilled programmer from nothing to something; to make the experience of launching an online application enjoyable.</p><p>Jeffrey Way, a well-known PHP developer and vocal Laravel evangelist, <a href="https://laravel-news.com/2014/06/the-artisan-files-jeff-way/">says he had a “gut feeling”</a> about Laravel. Taylor’s “instincts were simply different,” he says:</p><p>“I had the distinct impression that he understood something that most framework/library maintainers don’t: at the end of the day, Laravel is a product. This means, while the code is of course most important, developer happiness, ease of use, flexibility, and branding are equally vital…Laravel made coding fun, regardless of your skill level.”</p><p>One of Laravel’s mottos is “developer happiness from download to deploy.” Over the lifetime of Laravel thus far, Taylor and the open source community have continually updated and improved the framework, which remains free to use.</p><p>A large and passionate community has grown around the framework, and Vehikl is a proud part of that community. We not only use Laravel in building applications for ourselves and for our clients, we’re active in the open source community and enjoy supporting, attending, and sponsoring conferences, including the official Laravel conferences, Laracon US and Laracon EU. Laracon US began with around 70 attendants in 2013 and has grown to over 500 in 2015 and 2016, reflecting the growth of Laravel and its community.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d55970885bc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vehikl-news/a-brief-history-of-laravel-5d55970885bc">A Brief History of Laravel</a> was originally published in <a href="https://medium.com/vehikl-news">Vehikl News</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>