<?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 Najaf Ali on Medium]]></title>
        <description><![CDATA[Stories by Najaf Ali on Medium]]></description>
        <link>https://medium.com/@alinajaf?source=rss-36a609325382------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Qds7GM4Senu1estI7JDI3A.jpeg</url>
            <title>Stories by Najaf Ali on Medium</title>
            <link>https://medium.com/@alinajaf?source=rss-36a609325382------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 14:34:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alinajaf/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 and how we do one-to-one meetings]]></title>
            <link>https://medium.com/happy-bear-software/why-and-how-we-do-one-to-one-meetings-bb351eb9ef09?source=rss-36a609325382------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb351eb9ef09</guid>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Najaf Ali]]></dc:creator>
            <pubDate>Tue, 02 May 2017 17:05:59 GMT</pubDate>
            <atom:updated>2017-05-02T17:05:59.860Z</atom:updated>
            <content:encoded><![CDATA[<p>One-to-one meetings are a standard at more or less any software development team. Some of them have strict formats and agenda’s, while others are open-ended. Some teams do them weekly, fortnightly, or even monthly. Some teams don’t do them at all.</p><p>At Happy Bear Software, they are often the only opportunity we have to speak one-on-one outside of the context of a specific client project. They serve a number of purposes for us.</p><p>Firstly as a remote team working on disparate projects for multiple clients, we don’t often get a chance to talk. It’s probably good to be reminded that you work for us and not for the client, so our one-to-one meetings give us a rare chance to speak to each other when client work is humming along as expected.</p><p>Our one-to-one meetings are a chance for developers to raise any issues, concerns, or problems they might be having. This could be to do with the client project they’re working on, or perhaps their situation at home. Sometimes it’s enough just to talk about these issues, but where possible it’s a chance for me to take concrete steps to address any problems that might have cropped up.</p><p>Sometimes a one-to-one meeting is just there to catch up and build rapport. While this may not seem like the most business-minded way to spend your time, people will respond more favourably towards you if you have a rapport with them. This rapport also comes in handy when you have bad news or negative feedback to deliver. If your track record is 99 meetings where everything was fine then meeting 100 where you have to raise concerns about performance isn’t as difficult as it might have been. That feedback or that bad news is only one part of a longer relationship.</p><p>At times in the company we’ll want to try out new initiatives that might be controversial, or at least require buy-in from the entire development team. Rather than making a big announcement, proposing a plan and charging forward, one-to-one meetings are an opportunity to quietly build consensus. If you raise an idea and ask for concerns directly in your one-to-one meetings, then you’re much better prepared to affect real change in your team. After talking to your entire team individually and registering any issues they raise, your plan is far more likely to be well-received.</p><p>I have been a developer for the vast majority of my career. I’m only just getting into management, and am learning a ton of other things about finance, sales, marketing, and anything else I need to run a company. Sometimes it can be useful to get feedback on my performance and my behaviour from the development team. One-to-one meetings are a great place to ask for this kind of feedback and discuss the implications.</p><p>On the other hand, if there’s some feedback I need to give to a developer about their performance at work, then one-to-one meetings can act as a good place to do this. At the same time my preference is to set out the details of any negative feedback in text first (usually via an email) and have a discussion after we’ve both had time to digest and ruminate about it first.</p><p>We hire good developers, and while we accept that the average tenure for developers in this industry is around three years, we want to do everything we can to keep them around for longer than that. For this, the absolute minimum work we need to do is to do whatever I can to help the developers on our team meet their career goals. Some want to contribute to open source, others want to be famous conference speakers, yet others want to gain deep expertise in a specialty topic. One-to-one meetings are the exact right place to discuss these career goals, make plans, set targets, and stay accountable to them.</p><p>We carry out one-to-one meetings like we do all of our meetings, using remote video call, usually with appear.in. The only real preparation I do for the one-to-one meeting is to write a few bullet points about things it might be worth discussing. While we’re not averse to the idea, there’s no formal agenda for exactly what points a one-to-one meeting has to cover just yet.</p><p>We prefer to have one-to-one meetings once every two weeks. Once per week is a little too often and once per month is not quite often enough, especially to surface issues on client projects which usually need to be dealt with more quickly. This might become unmanageable on a larger team, but for now this interval suits us.</p><p>While our one-to-one meetings are free-form, I try to ask a number of questions at every meeting. Whether I actually ask them is usually down to whether I remember to in the moment, I’m not marking these off a checklist for example:</p><ul><li>How are you?</li><li>How do you feel about your client work?</li><li>Is there anything the company could be doing better?</li><li>How do you feel about your productivity?</li><li>Are you having any issues with other people in the company?</li><li>How are things outside of work?</li><li>Is there anything else you’d like to discuss?</li></ul><p>The final question “is there anything you would like to discuss?” is one I like to ask at the beginning, the middle, and at the end of the meeting. Whenever I ask it I try to pause long enough to make it feel awkward. I really want whoever I’m speaking with to raise even the smallest of issues, so I press them on this multiple times.</p><p>We can’t claim to have the best one-to-ones and I don’t think one-to-one meetings will magically fix a dysfunctional development team. However they act as the medium your relationship with your development team is played in. If you have an open, collaborative relationship with your developers and aim to act in each others mutual interests, then one-to-one meetings can act as a place for those things to happen.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb351eb9ef09" width="1" height="1" alt=""><hr><p><a href="https://medium.com/happy-bear-software/why-and-how-we-do-one-to-one-meetings-bb351eb9ef09">Why and how we do one-to-one meetings</a> was originally published in <a href="https://medium.com/happy-bear-software">Happy Bear Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automated testing at Happy Bear Software]]></title>
            <link>https://medium.com/happy-bear-software/automated-testing-at-happy-bear-software-bf4f0941daf0?source=rss-36a609325382------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf4f0941daf0</guid>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Najaf Ali]]></dc:creator>
            <pubDate>Mon, 01 May 2017 20:34:22 GMT</pubDate>
            <atom:updated>2017-05-01T20:34:22.471Z</atom:updated>
            <content:encoded><![CDATA[<p>How you test your code is a highly contentious topic for developers. At our company we give developers full autonomy to decide on a testing strategy based on the details of the project they’re working on. But just like magazines and publications have a “house style” for how they write, we have a generally accepted way of testing Rails applications.</p><p>Our recommended testing strategy has the goal of being good enough most of the time. It won’t be perfect in all cases, and that’s why we allow developers the free choice to use whatever tools they deem necessary. But for Rails applications, we can usually get by with this standard set of tools without much variation.</p><p>For us, two sets of tests are important. These are acceptance tests and unit tests. These are also commonly referred to as “feature specs” and “model specs” in RSpec.</p><p>For our acceptance tests we use a combination of RSpec and Capybara. We use these tools to exercise the application in a similar way to how a real-life user would. Capybara allows us to navigate the application in a separate process, filling in forms, clicking buttons, and making assertions about the content.</p><p>We want acceptance tests to be “end-to-end”. This means that we test the interaction as seen from the outside of the application. When a user clicks a button to create a new comment, we test that the user sees their data updated (rather than test that the data has changed in the database).</p><p>This also means that we stay within the boundaries of our application. If in the normal running of our application we have to interface with third-party services like APIs or email providers, then this is mocked out as part of the test.</p><p>One of the most important reasons we have feature specs is to maintain a productive development speed. Software is incredibly complex. Building a new feature can inadvertently break three or four features you built before. Having a set of automated acceptance tests gives you a warning when that happens. If you’ve changed the software somehow and it’s causing your tests to fail, you know something is broken and you can track it down to fix it. Without automated acceptance tests, development slows down and the end product is less reliable.</p><p>For our unit tests, we use RSpec. Unit tests are there to test methods on model classes in our Rails applications and to test any other classes we’ve created in order to deliver the functionality of the Rails application. These could be things like commonly used patterns like Presenters or Services, or any arbitrary classes we decide to define.</p><p>Using a combination of acceptance and unit tests, we like to practice what’s commonly referred to as “outside-in” development. “Outside-in” is loosely defined, but in principle it plays out something like this.</p><p>When a client or stakeholder defines a feature for us to work on, we try to come up with a mutually negotiated list of “acceptance criteria” for that feature. This serves as a list of what it means to complete a given feature. If everything in the acceptance criteria is complete then the feature is “done”.</p><p>There are many ways to write acceptance criteria, but for us a list of sentences is usually good enough. Here’s what a list of acceptance criteria for creating a blog post in a CMS might look like:</p><blockquote>• When the user clicks on “New post” they should see a form<br>• The form should allow the user to fill out the “name” and “body” fields<br>• When the user submits the form with a valid name and body, they should be redirected to the posts index and see the message “post created successfully”<br>• When the data is invalid, they should instead see a list of error messages</blockquote><p>As a developer, it can sometimes be difficult to know where to start when creating a new feature. Do you dive into the model and start implementing the database schema you’ll need for the feature? Do you start with the view? The routing layer? The controllers?</p><p>Outside-in development suggests that you start with the feature spec, implementing one of your acceptance criteria at a time. So for this create blog post feature, we’d begin by writing a test that clicks on a “New post” button. We’d then run that test and watch it fail because there is no “New post” button. We’d add the button, pass the test, and then move on to testing the next acceptance criteria, implementing enough of the feature to pass the test at each stage. When we have to drop down to writing model code or any code that doesn’t explicitly deal with the request/response cycle, we write the requisite unit tests too.</p><p>Developing in this way means that we have a clear, repeatable, obvious place to start when delivering features. Since it works directly on the acceptance criteria, it makes it easy to stay focused on exactly what the client wants on the feature (rather than straying off the path and working on nice-to-haves). It also makes sure that you implement exactly what you need for the feature and nothing more.</p><p>Once you’ve completed all the acceptance criteria using the Outside-in method, you can then focus on things that are more difficult to test. You can work on the front-end and make it match up to a design you’ve been given. You can refactor the code to make it more performant, less complex, or more secure. You can change it however you want, so long as your tests still pass.</p><p>If your tests still pass it means your acceptance criteria are met and your work on this feature is done. When the acceptance criteria are translated directly into tests in this way, they make the requirements decided on by you and the client a first-class citizen of your codebase.</p><p>Taken on its own this is a powerful way to structure your development with a lot of benefits. But also consider what it would be like if your entire application was built from features developed in this way. The result would be a suite of automated tests that fully exercise the functionality that your client has ever defined for the system. That makes it more reliable, more like what the client actually wanted, and much easier to change over time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf4f0941daf0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/happy-bear-software/automated-testing-at-happy-bear-software-bf4f0941daf0">Automated testing at Happy Bear Software</a> was originally published in <a href="https://medium.com/happy-bear-software">Happy Bear Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The programmer career middle-game]]></title>
            <link>https://medium.com/happy-bear-software/the-programmer-career-middle-game-c7381cde022e?source=rss-36a609325382------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7381cde022e</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Najaf Ali]]></dc:creator>
            <pubDate>Tue, 17 Jan 2017 16:55:30 GMT</pubDate>
            <atom:updated>2017-01-17T16:55:30.960Z</atom:updated>
            <content:encoded><![CDATA[<p>You’re a programmer about ten years into your career. You’ve worked on countless projects, watched teams do all the wrong things, watched teams do all the right things, and have been somewhere in middle most of the time. You still like making things, but are weary of solving the same problems yet again for someone else’s business. You’re good at your job and that’s why you find it boring sometimes. You’d like to have a bigger impact than just the specific lines of code you write.</p><p>I call this the developer mid-career plateau. Unless you’re ecstatic about every waking moment of your job, this far into your career at least one or two of the things in that last paragraph will ring true for you. This is natural and I think something we all go through. Most of my friends in the industry are at this stage of their career.</p><p>This post is not advice, and the word-choice and distinctions in the topics below are coloured by experiences and the people that happen to be in my network. In this post I’m going to list potential <em>directions</em> for you to go in, rather than recommend that you do one thing over another. There’s no right or wrong way to plan your career, as no one knows your priorities and goals better than you do.</p><h3>Keep doing what you’re doing</h3><p>One perfectly good option is to keep doing whatever it you happen to be doing. There are many benefits to being a line-of-business senior developer. You have an in-demand skill-set, and can focus on improving your technical skills further rather than learning completely new skills from scratch. You can expect a steady pay and don’t necessarily have to take on more responsibility than necessary. After a decade of this, you will strategies in place for dealing with ancillary problems like time management and so are probably at the most productive stage of your programming career.</p><p>There is much to envy in staying where you are, especially from the point of view of someone who has stepped into entrepreneurship or into a completely separate career path. Depending on what you want to get out of your career, there’s no shame whatsoever in staying where you are, being massively effective and getting paid accordingly.</p><h3>Consultant/freelancer</h3><p>In my definition, a consultant or freelancer is someone that codes for money who is not a full-time employee. Your sales process may eventually allude to “value-based” pricing but you’re effectively a time and materials contractor.</p><p>The difference between this and being a full-time senior developer somewhere is stability. You may not always be in work, and so your rates need to reflect this. Some people I know who try this like the idea that they’re not implicitly obligated to stay with a single company for the long haul. Others spend for example, half of the year freelancing and spend the other half on the beach in Bali.</p><p>There is plenty of work for freelance web development programmers around. Your ability to get it will depend either on having a strong network or on having good enough marketing ability to get work through your presence among your potential clients or people that can refer them to you.</p><h3>Lead Developer/Architect</h3><p>By this I mean someone that has a higher level of authority on their team in terms of making technical decisions and who thinks about how the systems an organisation is building interact with each other rather than the specific code in any one feature.</p><p>This is a great direction if you want to stay technical but also have a larger impact on the development teams you’re on. Depending on the details of the role, you will have a greater say in the norms and values of the team you’re on than if you were just a rank and file developer. You will have to think strategically on a monthly or even yearly timeline rather than the features assigned to you in a given sprint. The pay will probably be better. You’ll also be able to more easily put into practice the lessons you’ve learned in your career on somewhat less functional teams.</p><h3>CTO</h3><p>By CTO, I’m referring to the person that acts to facilitate collaboration between the development team and the rest of organisation. I’ve also heard this role labeled as “shit umbrella”. When the business drops a lot of a shit on the development team, it’s the role of the CTO to shield them from it and give them the information and resources they need to add value to the organisation.</p><p>As a CTO you will have the maximum impact possible in your organisation in an ostensibly technical role. It is however highly unlikely that you will be writing any code or involved in any day-to-day technical decisions.</p><p>If your goal is impact, then this is great direction for you to go in. It will involve dealing with people and understanding parts of the business that you have no expertise in. Just like in any organisation, it will probably involve a lot of politics. Experience as a full-time CTO will also prepare you for a lot of the other directions you might go in, including entrepreneurship or advisory roles.</p><h3>Product Manager</h3><p>Product management is a multi-disciplinary role, sometimes described as the “CEO of the Product”. It’s a role helped by understanding of business fundamentals, software project management techniques, a bit of programming, a lot of UX, and practical communication skills. You will be spending a lot of time getting people in line with a strategy or roadmap and seeing it through to completion.</p><p>Product management is a great role for former programmers, as they have a far better understanding of the technical implications of product decisions than non-programmers will. It will however require that you spend a lot of time improving your skills in other areas that will help you work with the impact of product decisions on the business and on the user.</p><p>Learning product management is a sidestep out of programming and into a form of management, and can lead to other non-technical career paths. It’s also a great primer for entrepreneurship, as it forces you to contend with business fundamentals in a way that a pure technical role won’t.</p><h3>Entrepreneur</h3><p>Starting your own business, be that an technical consultancy, a SaaS product, or a fish and chip shop, is probably the most difficult direction to go in on this list. It means completely shedding the stability of a steady pay in favour of an unknown future upside.</p><p>Most entrepreneur’s have no programming ability. In the right context, your technical skills are a superpower. The company you work at right now, either as a freelancer or as a full-time employer is that context. When you start your own business, you are no longer able to focus solely on your superpower, you have to build the context it operates in too.</p><p>Doing so requires an understanding and appreciation of the five major parts of any business: value creation, value delivery, marketing, finance, and sales. You’ve spent your entire career in one of these areas. You are entry-level in all the others. You need to get good enough at those other things that you can hire people to do those things for you.</p><p>One way of solving this problem would be to team up with co-founders. This increases your likelihood of success because you’re now able to play to your various strengths and support each other through the emotional ups and downs of running a business.</p><p>This is a great direction to go in if you value autonomy and building long-term economic advantages for yourself. It’s not a great option if you like stability.</p><h3>Technical advisor</h3><p>There are many startups that have good business fundamentals but have no idea where to start when it comes to building software. Startups often trade a bit of equity or a monthly fee for regular access to an advisor, typically with some specialist knowledge or experience.</p><p>Your experience is probably useful to early or seed-stage startups. Having someone with technical experience to help guide the development of their software is valuable to them. If you can help with high-level architecture, hiring, and building a positive engineering culture, you’re worth whatever they’re paying you.</p><p>These engagements typically take a day or two per month of your time. Depending on how you’re compensated, this might be a good source of income or expose you to a small upside in startups. The latter may work well if you have such an arrangement with five to ten startups.</p><p>This is a great direction to go in if you want to simultaneously build your network and get exposure to a number of problem domains without having to spend every waking moment at one particular company. It allows you to make the good judgement you’ve developed over the years available for others, and therefore potentially makes a larger impact than if you were working at just one company.</p><h3>Specialist</h3><p>By a specialist, I’m referring to someone that has niched down into a specific technical expertise. This is usually less to do with programming language or framework and more to do with a specific technical application. Examples might be computer graphics, information retrieval, natural language processing, cryptography, compiler design/PL theory, bioinformatics, or machine learning.</p><p>By specialising in a hard technical topic, you make a number of career avenues available to you. You might find a full-time job were your particular skill set is in demand. You might find it more appropriate to set up as a consultant or freelancer in your niche, which can end up being far more lucrative than a freelance line of business web developer. You may go an extra step and set up a consulting practice focusing on that niche.</p><p>This direction is good if you want to double down on your technical skills and become known as an expert in a specific field. It is a solid career choice, as your skills will be in greater demand and that gives you a degree of autonomy you otherwise wouldn’t have.</p><h3>Leaving the industry</h3><p>At some point, you may feel like you’ve spent a bit too much of your life looking at dark screens filled with coloured text. Many programmers feel an urge to stop doing programming as their main source of income and move completely to another industry focus.</p><p>I know of only a few people who’ve done this but they seem to be happy about their decision. Software touches everything, so it’s unlikely you will be able to completely escape computers.</p><p>This is the only direction you have if you’re tired of doing software-related things for money, but it’s one you should seriously consider if you don’t feel a career in this industry will make you happy.</p><p>I don’t have any concrete answers about what you should or shouldn’t do later in your career as a developer. I’m still trying to navigate this particular jungle myself. Most of my friends in the industry are in the same place.</p><p>We’re all doing bits and pieces of things I’ve described above. We might do a bit of consulting, work as a CTO for a few years, then try our hand at running a business. That’s what a modern career around building software looks like.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7381cde022e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/happy-bear-software/the-programmer-career-middle-game-c7381cde022e">The programmer career middle-game</a> was originally published in <a href="https://medium.com/happy-bear-software">Happy Bear Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HBS Relational databases topic guide]]></title>
            <link>https://medium.com/happy-bear-software/hbs-relational-databases-topic-guide-7cbd2be501dd?source=rss-36a609325382------2</link>
            <guid isPermaLink="false">https://medium.com/p/7cbd2be501dd</guid>
            <category><![CDATA[database]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Najaf Ali]]></dc:creator>
            <pubDate>Tue, 17 Jan 2017 14:45:04 GMT</pubDate>
            <atom:updated>2017-01-17T15:53:00.509Z</atom:updated>
            <content:encoded><![CDATA[<p>Working with relational databases is part of the core skill set for full-stack developers at Happy Bear Software. It’s a topic that new developers get to last because it’s seen as “back-end” and perhaps more difficult than front-end development. While it may require more imagination and visualisation ability to master, it’s nevertheless an essential part of of web developers toolkit.</p><p>Relational databases represent the core data model of your web application. How you structure a relational database in your application has a significant long-term effect on how that application will work. The right structure will lend itself more easily to modification and extension later. The wrong one will lead to architectural, performance-related, and other limitations very quickly.</p><p>This article drills down into the specifics of what we expect developers to know while working at Happy Bear Software. For each sub-topic, we’ll list what the thing is, why you should know the thing, and how to get better at the thing if you’re not already good at it.</p><p>The things are, in no particular order:</p><ul><li>ACID</li><li>Basic SQL for CRUD</li><li>Designing relational databases</li><li>Querying relational databases</li><li>Query Performance</li><li>PostgreSQL</li><li>ActiveRecord and ORMs</li></ul><h3>ACID</h3><p>ACID stands for Atomicity, Consistency, Isolation, Durability. It is a set of properties of database transactions. Relational databases that we use to deliver software will satisfy some or all of these criteria.</p><p>You should understand ACID because you’ll often be presented with the choice of what data store to use in a given project. Non-relational databases typically sacrifice one or more of the ACID guarantees to better suit a specific use case. In order to make an intelligent decision either way, you’ll need to understand what ACID guarantees are and the implications of sacrificing one or more of them.</p><p>A good start is to read <a href="https://en.wikipedia.org/wiki/ACID">the wikipedia page on ACID</a>, and to look for articles about how and to what degree ACID is implemented in RDBMS’s like PostgreSQL, MySQL, and Oracle.</p><h3>Basic SQL for CRUD</h3><p>SQL stands for Structured Query Language, and is the pre-dominant interface you will use for interacting with relational databases. CRUD stands for Create, Read, Update, Delete. Aside from manipulating a database schema itself, these are the operations you will use SQL for.</p><p>You should learn to do basic CRUD operations in SQL because these are the SQL statements that web applications you create will be sending to the database they’re integrating with. Without knowledge of how those SQL statements work (beginning with how to write them yourself) you won’t be able to reason about their operation in terms of functionality or performance.</p><p>You should learn basic SQL by working through an introductory text, including plenty of exercises that get you writing queries by hand in an SQL prompt. At this level, there’s little difference between the most commonly used database systems, so SQLite is fine to start with.</p><h3>Designing relational databases</h3><p>The design of a relational database is the high-level architecture of a web application. When talking to a potential client about a feature, you may already be mentally visualising what the data model would look like. Relational databases are designed to handle just about any use case you can come up with, provided you get the design of the schema right.</p><p>Relational database design gives you a number of tools to put to use when designing a schema. One-many relationships model one thing being related to many other things. Many-many relationships model two-way relationships with many things related to zero or more many other things, often using a join table. Parent-child relationships model things in the same table related to one other thing in that table. Database normalisation gives you a framework for thinking how to decide what fields should go in what tables so that the database is overall more amenable to good operation and future change.</p><p>To learn to be better at relational database design, read about these topics in depth and do plenty of design exercises. Read about “normal form” (no need to understand it in depth, but it’s worth reading through the first three stages). Think about how you would model Eventbrite, GitHub, Twitter, or other services you use. What would be a many-one relationship? What would be many-many? Write out the SQL required to create your database schema designs and run them, just like you would with a programming exercise.</p><h3>Querying relational databases</h3><p>Besides the basic ability to read fields out of database, much of the power of using a relational database lies in the ability to query it in ways you won’t foresee at the design stage. Your ability to query the database in flexible ways while still being performant will depend heavily on how you designed the schema.</p><p>At the most basic level, querying a database schema involves selecting, filtering, and ordering the data you want from a single table. More advanced queries using inner/outer left/right joins allow you traverse different tables, returning data in a second table “joined” to data in a first. SQL also provides aggregate functions that allow you to count, sum, average, and perform other operations produce a single value from a set of data. Yet more advanced queries can be built by using the result of one query as part of another, a facility known as subqueries.</p><p>You should learn these techniques because they will often be put to use in the web applications we build for our clients. In some cases you will be writing these queries by hand and in others an ORM will be generating them for you. Without an understanding of how non-trivial queries are put together, it will be difficult for you to reason about the capabilities of a relational database system. Understanding how these queries work may also inform your database schema design decisions and help you make good decisions about query performance.</p><p>You can learn how to write these queries by practicing. You can do this using sets of exercises like <a href="https://sqlbolt.com/">SQLBolt</a>, by doing exercises out of books, or by getting access to publicly available data and experimenting with SQL queries on it.</p><h3>Query performance</h3><p>The performance of SQL queries is a complex topic. Your role will be to determine what there performance characteristics of the SQL your application runs are and take steps to make those performance characteristics better.</p><p>This will involve looking at the queries being made to the database and using debugging tools to analyse how the database is executing those queries (typically the query planner). Based on this you will need to make decisions about creating/removing indexes of various types, keeping in mind the trade-off in terms of keeping those indices up to date.</p><p>A good place to start learning about query planning and indexing is the documentation of various database management systems. MySQL for example will have a different approach to optimising query performance than PostgreSQL will. There are also several books on the topic. You can also jump into most Rails codebases and identify at least one or two query performance issues that can be optimised by the intelligent use of indexes.</p><h3>PostgreSQL</h3><p>While it’s good to have a general knowledge of different relational database systems, the one we end up using the most is PostgreSQL. This is partly because it is the default database provided on our PaaS of choice, Heroku. It’s also because it’s a rock-solid piece of software that has been around for thirty years. For the vast majority of the software you will build with us, PostgreSQL will handle all of your use cases just fine.</p><p>You can learn more about PostgreSQL by working through documentation, books, and any other written material you can get your hands on. Get it running locally and do all the exercises you’re using to learn SQL in PostgreSQL if you haven’t been doing so until now. Have a look at the special index types that it makes available to you that other databases don’t. The JSON data type is another PostgreSQL specific feature it may be worth getting acquainted with.</p><h3>Using ORMs like ActiveRecord</h3><p>We’re a Ruby on Rails consultancy so much of your interaction with the database will be via the ActiveRecord ORM. Using ActiveRecord effectively is a skill in itself that it’s worthy of your time to spend developing.</p><p>Learn how migrations work. In addition to the documented interface, have a look at how indexes are created and how you might create some of the more esoteric index types in PostgreSQL using the ActiveRecord migration interface. If you can’t bend the migration code to your will, can you make it so that you can send raw SQL to do what you want?</p><p>Learn the ActiveRelation query interface, and take a look at the query that gets output to the database. This information is usually available in the development logs, or you can get it inline by calling `.to_sql` on an ActiveRelation object. Learn to name parts of a relation and group them into chainable named scopes.</p><p>More generally, think about the queries that the ORM is generating and what this means for the performance of your application. Here we’re talking not about the performance characteristics of a particular query, but instead the number of queries your application is sending to the database. If you’re getting a big list of records, only to iterate over and do an additional query for each one, you’ve run into the classic N+1 query problem, for example. A single query represents a trip across the network, so one single query loading tons of data is almost always better than lots of queries loading a small amount of data.</p><p>Learning how and how best to use an ORM like ActiveRecord takes time and experience. The relevant<a href="http://guides.rubyonrails.org/"> Ruby on Rails Guides</a> are a good place to start, but the only meaningful way to get practice with it is to create real software with it.</p><p>That’s a broad overview of the range and extent of skills and knowledge we want from developers at Happy Bear Software. I’ve left a lot of things (e.g. stored procedures, views, constraints) off this list that may be useful but we just haven’t seen come up yet on client projects. This list, the specific points of emphasis and the guides to improving could also do with a bit of work. This article should however give you ideas for where to improve your abilities with databases if you have time to focus on them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7cbd2be501dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/happy-bear-software/hbs-relational-databases-topic-guide-7cbd2be501dd">HBS Relational databases topic guide</a> was originally published in <a href="https://medium.com/happy-bear-software">Happy Bear Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Questions to ask in your developer job interview]]></title>
            <link>https://medium.com/happy-bear-software/questions-to-ask-in-your-developer-job-interview-850de59c5fc7?source=rss-36a609325382------2</link>
            <guid isPermaLink="false">https://medium.com/p/850de59c5fc7</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[interview]]></category>
            <dc:creator><![CDATA[Najaf Ali]]></dc:creator>
            <pubDate>Sun, 15 Jan 2017 23:51:07 GMT</pubDate>
            <atom:updated>2017-01-15T23:54:04.468Z</atom:updated>
            <content:encoded><![CDATA[<p>In job interviews, there comes a point when the interviewer asks you for questions. Most candidates answer “no”. Sometimes they answer with one or two questions for the information they think they need about the company and the offer.</p><p>This is an enormous waste. Until this point, the interviewer has control of the conversation. They ask you a sequence of questions, with the goal of assessing your suitability as a candidate. When they ask for your questions, they are handing control of the interview over to you. You can do much better than just a couple of sheepish informational queries here.</p><p>You should have two overall goals in your job interview. The first is to get an offer from the company. Asking intelligent questions can go a long way to demonstrate how you think, what you value, and other positive characteristics you have that the interviewer might have missed. At most companies, all of this will lead to a higher chance of you getting the offer.</p><p>Your second goal is to find out as much as you can about the company. You want to do this because making the decision to start work at a company will have a huge impact on your career and quality of life. Spending even a short probationary period at this company is a one to three month chunk of your CV for this year. You may end up spending years of your life here, spending more time with your coworkers than people you actually care about. The stakes are high, and it’s worth finding out as much as possible about what working at this company will be like before entertaining an offer. Asking questions at an interview can get you a first hand account of the working conditions and career progression from a a real-life employee of the company.</p><p>In this article I’m going to give you a list of questions that you should consider asking at the interview. You don’t have to ask all of them, and there’s no special wording I’m using here. These are just to get you thinking about what you should ask when you get to this stage of the interview. Come up with 5–10 questions of your own, using this list as an inspiration, put them in your notebook, and take your notebook into the interview.</p><p><strong>Can you describe how you spend a typical day?</strong> This gets the interviewer talking and gives you a quick reference point about one employees day-to-day activities at the company. Depending on their role, you might want to worry if e.g. they spend all day in meetings, or don’t go to any meetings at all, or have to turn up very early/stay very late to get any work done.</p><p>How is development time split between firefighting, maintenance, and <strong>feature development?</strong> Here you’re asking about the proportion of time spent on each of these activities. Asking these questions shows that you have practical experience of actually working on a development team. Avoid workplaces that are too heavily weighted towards firefighting, it was likely a lack of adequate budget, expertise, or engineering culture that got them into that situation.</p><p><strong>What concrete steps does the company take to foster diversity and inclusion?</strong> Regardless of your politics, this is a good question to ask. How they answer will tell you a lot about the organisational stance towards these issues, giving you the information you need to decide whether you’re aligned with it. If the interviewer gives a concrete set of actions they’ve taken or is taken aback by the question, that answer carries information. If they are dismissive of the question, that answer carries information too.</p><p><strong>What are the medium to long-term goals of the company?</strong> Here you’re asking about medium to long term vision and strategy. This shows that you can think not only about your day-to-day work but the context within which it sits. The answer gives you two bits of information. Firstly if the interviewer can answer coherently at all, it indicates that the organisation is good at communicating it’s plan to everyone at the company. Secondly it tells you what the company will be focusing on in the medium and long term. You can use that information to determine how well the companies goals align with yours.</p><p><strong>Is there budget and time set aside for professional development?</strong> Asking this question shows that you’re interested in improving your effectiveness as an employee. The answer tells you how much support you can expect from the company in doing so. Many technology companies provide budget for workshops, books, conferences, and other training, and give you time to work on your skills in some form. The more of that the better.</p><p><strong>What is the company’s stance on working from home?</strong> Maybe you like the idea of working remotely and maybe you hate it. This question tells you what you need to know about this company either way. A company that is 100% in-office is fine. A company that is 100% remote is fine. The difficulty comes in office/remote hybrid situations if the office becomes a privileged area for communication. These difficulties can be addressed, but you’ll want to question further to make sure they have been.</p><p><strong>How often do you deploy to production?</strong> In the right company, this question hints at an opinion about how software should be released. Many tech companies deploy their production applications multiple times a day, though this requires a commitment to automated testing with infrastructure set up to run all of those tests before a deployment. Other tech companies might deploy every week, every fortnight, once a month, or at even larger intervals. You probably want the former.</p><p><strong>Can you describe the stages a feature or change has to go through from requirements gathering through to deployment to production?</strong> Here you’re asking about the development process. This again indicates that you’ve done this job before. Since you’re going to be plugged into this development process, it’s important that you’re on board with the status quo, at least to begin with. Too little, too much, or needlessly time-consuming process can all be bad signs.</p><p><strong>How early in the requirements gathering process are the development team consulted? What format does that take?</strong> Here you’re really asking about what the relationship is like between the development team and the rest of the company. Is it collaborative, with the development team brought in to inform strategic decisions before they get into a backlog? Is it adversarial, with requirements dropped “over the wall” for the development team to work on?</p><p><strong>What is the development team’s stance towards testing?</strong> At face value this will tell you a bit about the engineering culture at the company. It also tells you how willing the company is to invest in the quality of the software you’re producing. Additionally, if the conversation switches to one about test coverage, dogmatic adherence to “best practices”, or hero worship of programming gurus, you’ll know to avoid that too.</p><p><strong>Does the development team do code review before deploying code to production?</strong> Code review is a highly effective way for a team to share knowledge and establish a set of shared technical norms and values across a development team. Asking about them and how they’re done should tell you a bit about how the development team communicate with each other.</p><p><strong>How often do you do one to one meetings?</strong> Doing regular one-to-one meetings is the absolute basic minimum required to run a functional team of any kind. Asking this question should give you an idea of how good the company is at management. If they don’t do one-to-one meetings, you can ask about how employees give feedback to managers and team-leads.</p><p>This is a relatively small sample, but should give you enough to begin a meaningful conversation with your interviewer about what working for their company will be like. Use them, don’t use them, come up with your own questions, but whatever you do, <strong>use this moment to take ownership of the interview</strong>. Guide the conversation to topics that indicate that you’ve done this job before and give your more information about the job at hand.</p><p>This won’t guarantee an offer, but it will make it more likely. When you get the offer you’ll also be much better positioned to decide if it’s one you want to accept. These are all good things for both you and for the company.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=850de59c5fc7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/happy-bear-software/questions-to-ask-in-your-developer-job-interview-850de59c5fc7">Questions to ask in your developer job interview</a> was originally published in <a href="https://medium.com/happy-bear-software">Happy Bear Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to argue for better software security]]></title>
            <link>https://medium.com/bear-claw/arguing-for-better-software-security-a5a58f4c7048?source=rss-36a609325382------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5a58f4c7048</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Najaf Ali]]></dc:creator>
            <pubDate>Wed, 11 Jan 2017 14:45:16 GMT</pubDate>
            <atom:updated>2017-01-11T14:50:33.475Z</atom:updated>
            <content:encoded><![CDATA[<p>Software security is hard. Developers don’t focus on security regularly. Before you can begin to make your software secure, you have to convince your organisation, your team, and yourself that security matters at all.</p><p>In this article I’m going to give you ammunition for that debate. I’ll argue from multiple angles that software security is worthy of your time, focus, and effort. As someone that talks to my clients about security regularly, I’ve had to develop these arguments to contend with people who aren’t motivated to act on security. Hopefully you’ll find use for these arguments too.</p><p>There is a well-established argument from capitalist self-interest. If your software suffers a major public security breach, this puts you at a number of disadvantages as a company. Your investors will lose confidence in your continued operations. Your customers will feel less inclined to use your offering, for fear of the potential negative impact of a security breach on them. Your engineering team might find recruitment more difficult if your company has a reputation for technical incompetence. All of these problems are multiplied when a company is unprepared to handle the PR fall-out of a security incident.</p><p>Additionally, if your company operates in a domain who’s technical operation is regulated, you may have legally enforced obligations to comply with some established standard. This line of reasoning usually leads to the most cynical security theatre, so you would want to include this in a broader conversation about security rather than on it’s own.</p><p>This set of arguments is best employed with non-technical management. It works better with details of three well-chosen examples of security breaches, noting the bottom-line impact the breach had on the company in question. Your goal in doing so is usually to secure budget or time allocations for your development team to focus on security.</p><p>There is an argument from professionalism. Software engineers talk about “craftsmanship” in reference to their work. They, in theory, take pride in creating high quality software.</p><p>There are many axes along which we can measure software quality. While I’m not in total agreement with the emphasis, groupings and vocabulary used, <a href="https://en.wikipedia.org/wiki/ISO/IEC_912">ISO/IEC 9126</a> lists a few of the attributes of good software. Security is one of them. Any professional software team should be taking steps to improve the quality of the software they are providing to their users in a broad range of the categories described therein, including in terms of security.</p><p>Software with fewer bugs is higher quality software. Security flaws in your software are a specialised type of bug. By that reasoning, more secure software is also higher quality software. Since we’re all professional software craftspeople, we all want to make higher quality software. One of the ways we can do that is to make software more secure.</p><p>The argument from professionalism is appropriate when working with the development team responsible for creating and maintaining an application. They go well when coupled with a few low-cost habits or practices that can quickly improve the security of their code, to at least get them thinking about security regularly.</p><p>Lastly, there are arguments from ethics. As someone with the ability to do something that could prevent a security breach, it could be argued you are ethically obliged to take any such action, or at least make a best effort attempt to do so.</p><p>Your employer would suffer in the event of a (badly handled) security breach. As an employee there is likely a clause in your contract to the effect of an obligation for you to act in the interests of your employer. You’re therefore contractually obliged to better prepare for, prevent, detect, and respond to security issues.</p><p>Depending on the type of security breach, you personally or your development team may suffer. This might be through data disclosure, fraud, or perhaps simply the blame that your team will get for letting the breach happen. While there’s no legal obligation here, you might feel the personal instinct for self-preservation, and for protecting from harm those who work closest to you.</p><p>Your users may suffer in the event of a security breach. They may also suffer personal security issues thanks to an otherwise correctly functioning parts of your application too. There is highly likely to be an all-caps clause disavowing any liability for damages in the terms of service document that your users will agree to when purchasing your software. There is therefore no legal reason for you (short of some domain-specific regulation) to focus on security.</p><p>However if you care about the impact of your work, it might bother you that users are suffering from fraud, blackmail, or other wrongdoing in part because of software that you created. These are likely to be the people paying your salary. Perhaps you are fine with this state of affairs, or are happy to shift responsibility to your employer.</p><p>The general public, users of the internet at large, may also suffer thanks to lapses in your security practices. Modern computers are general-purpose. Once compromised, they can be used for just about any function. If an attacker gains control of your infrastructure, they can sell that control on to the highest bidder. The computers that serve your application may simultaneously be used to host a human-trafficking site, distribute indecent images of children, or participate in a distributed denial of service attack.</p><p>Again, this may not cause you to take pause, especially if you’re happy to leave all responsibility for the impact of your work with your employer. However all of these arguments are worth considering when trying to convince others to take security seriously.</p><p>The arguments from ethics can be used when discussing these issues with just about any one who has a moral compass. In practice, these arguments are less convincing than the arguments from professionalism or from self-interest. However they are useful to mention to your peers in the industry if you know that you’re of the same political/moral leanings and are already convinced that your listener will see the merit in them once they’re raised.</p><p>So those are the arguments I use to get people to focus on security. I try to pick an appropriate line of reasoning depending on the context. It is some combination of capitalist self-interest, professionalism, or ethics. These arguments can provide a basis for discussion on allocating more time, attention, budget, or other resources on focusing on security.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5a58f4c7048" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bear-claw/arguing-for-better-software-security-a5a58f4c7048">How to argue for better software security</a> was originally published in <a href="https://medium.com/bear-claw">Bearclaw</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[So you want to learn web security?]]></title>
            <link>https://medium.com/bear-claw/so-you-want-to-learn-web-security-35594d62269?source=rss-36a609325382------2</link>
            <guid isPermaLink="false">https://medium.com/p/35594d62269</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Najaf Ali]]></dc:creator>
            <pubDate>Wed, 24 Aug 2016 15:03:35 GMT</pubDate>
            <atom:updated>2016-12-10T23:09:04.507Z</atom:updated>
            <content:encoded><![CDATA[<p>For better or worse, I’ve positioned myself as an expert on web application security. This is worrying for me, as I’ve never worked for a security company. I’ve never worked alongside pen-testers and have had no real mentoring on the topic. All of my security knowledge is self-taught.</p><p>At the same time, at <a href="https://gobearclaw.com/">BearClaw</a> I do vulnerability assessments for clients and consistently find security flaws in code that their own development team missed. This means I’m probably OK at security, or at least one or two steps ahead of the average web application developer.</p><p>I often get asked by developers where to start when they want to improve their security skills. Rather than respond to each of them individually, I’m writing this post with my collected advice on how to start writing more secure software.</p><h4>1. Read the <a href="http://mdsec.net/wahh/">Web Application Hackers Handbook</a></h4><p>This is the bible of web application security. Any vulnerability you find in your own code is likely to be a variation of a vulnerability already documented in this book. Read it cover to cover, take notes, and then keep it by your desk.</p><h4>2. Do lots of web security exercises</h4><p>It’s difficult to appreciate the impact of security vulnerabilities without being able to exploit the vulnerabilities yourself. Security exercises are an opportunity for you to do that in a safe environment where there’s definitely a vulnerability present for you to exploit.</p><p>Here are some good examples:</p><ul><li><a href="https://google-gruyere.appspot.com/">Google Gruyere</a></li><li><a href="http://overthewire.org/wargames/">Over the Wire</a></li></ul><p><em>Side note, did I mention we run a security workshop? People tell me this is a good workshop: </em><a href="https://ti.to/bearclaw/rails-security-workshop-september%E2%80%932016/"><em>https://ti.to/bearclaw/rails-security-workshop-september–2016/</em></a></p><h4><strong>3. Do the Matasano Crypto Challenges</strong></h4><p>If any developer ever asks me for any advice about anything, the second thing I usually say to them is “Do the <a href="http://cryptopals.com/">Matasano Crypto Challenges</a>”. I really want you to do the <a href="http://cryptopals.com/">Matasano Crypto Challenges</a>. You should do the <a href="http://cryptopals.com/">Matasano Crypto Challenges</a>.</p><p>Completing just the first three sets will put you in the tiny subset of programmers that have a semblance of a clue about cryptography in practice. Please do them, for my sake and for yours.</p><p>I want you to do them because they’re fun. They will make you terrified of doing cryptography, and this is a good thing. They will allow you to have coherent opinions about the cryptography you see put to use in the average web application. You will be armed with concrete reference experiences when making decisions about cryptography, rather than empty soundbites that other developers repeat to themselves.</p><h4><strong>4. Implement basic security mechanisms by hand</strong></h4><p>Think about the basic security mechanisms that most web applications implement and try coding them up from scratch. In particular:</p><ul><li>Registration (including password storage)</li><li>Login/logout</li><li>Password reset</li><li>Role-based authorisation (e.g. “admin” vs. “standard” users)</li></ul><p>Now think about how your implementation might be vulnerable. Is your password storage mechanism susceptible to brute forcing in case of a data breach? Can an attacker craft password reset tokens? Can your registration form be used to modify the data of any user? Can a user sneakily upgrade themselves from standard to admin using the forms on your site? If a user’s laptop is stolen while they’re logged in, is there a way you can log them out remotely?</p><p>Think about how to mitigate these vulnerabilities and how to write these features so they withstand security breaches at various levels. Look at the code of a library like Devise and think about how they avoid various types of vulnerabilities.</p><h4><strong>5. Go bug-hunting</strong></h4><p>Now that you’ve built up your skills, it’s time to put them into practice. Sign up as a hacker to <a href="https://hackerone.com/">Hacker One</a>, look for open bounties and see if you can find security holes in websites on production. You might earn a bit of money in the process. You’ll definitely learn something.</p><h4><strong>Bonus: Reading list</strong></h4><p>More books for you to read:</p><ul><li><a href="https://www.nostarch.com/tangledweb.htm">The Tangled Web: A Guide to Securing Modern Web Applications, Michal Zalewski</a></li><li><a href="https://www.schneier.com/books/cryptography_engineering/">Cryptography Engineering: Design Principles and Practical Applications, Niels Ferguson, Bruce Schneier, and Tadayoshi Kohno</a></li><li><a href="https://www.amazon.co.uk/Art-Software-Security-Assessment-Vulnerabilities/dp/0321444426">The Art of Software Security Assessment, Mark Dowd, John McDonald, Justin Schuh</a></li></ul><h4><strong>Closing note</strong></h4><p>If you get through all of that and are interested in doing both development and security assessments, send us an email to say hello: <a href="/service/mailto:contact@happybearsoftware.com">contact@happybearsoftware.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35594d62269" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bear-claw/so-you-want-to-learn-web-security-35594d62269">So you want to learn web security?</a> was originally published in <a href="https://medium.com/bear-claw">Bearclaw</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why you should send your developers to our security workshop]]></title>
            <link>https://medium.com/bear-claw/why-you-should-send-your-developers-to-our-security-workshop-665f0ef79327?source=rss-36a609325382------2</link>
            <guid isPermaLink="false">https://medium.com/p/665f0ef79327</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Najaf Ali]]></dc:creator>
            <pubDate>Mon, 15 Aug 2016 17:54:29 GMT</pubDate>
            <atom:updated>2017-07-17T13:30:01.315Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Note: the vast majority of our content is meant to be useful without you having to pay us any money. This article is an exception: it is 100% sales pitch. If that turns you off, you probably want to stop reading now and go back to whatever you were doing.</em></p><p><em>If you’re interested in either doing our security workshop in-house or sending your developers to a public one, please read on.</em></p><p>We run a regular one-day workshop that teaches developers how to identify vulnerabilities in Ruby on Rails applications. We teach them by giving them time-boxed challenges based on real-life vulnerabilities that they have to complete over the course of a day.</p><p>Here are the reasons why you should either send your developers to one of our public workshops or run a workshop with us in-house.</p><h4>Your developers will enjoy the workshop</h4><p>One of the most common items of feedback we get is that the workshop is <em>fun</em>. While they may have read blog posts or articles about security in the past, almost no developers have spent time actively hunting for vulnerabilities in their day-jobs.</p><p>We think it’s fun because it allows them to use their existing skills and knowledge in ways they may not have considered before. They’ve honed their ability to create software for years. For one day, they get to use those same skills to <em>destroy</em> software instead. Your developers will probably enjoy it too.</p><h4><strong>Your developers will stop vulnerabilities before they get to production</strong></h4><p>One of the goals of the workshop is to get developers to think about security before they ship code. We want them to have an intuitive distrust for all code around your basic security mechanisms, so they double check to make sure it leaves no open avenues for attack.</p><p>We do this by bombarding attendees with reference experiences. By the end of the day they will have attempted to bypass the security of eight Ruby on Rails applications. All of the applications are insecure in different ways. This teaches them to check for those insecurities in any code they write in the future.</p><h4><strong>Your developers will find security flaws in your code</strong></h4><p>All software has security vulnerabilities in it, and all developers write insecure code. That’s not up for debate. The only question is how much effort you put into finding and fixing security vulnerabilities in your software.</p><p>In the weeks after the first workshop, we received multiple emails telling us that attendees had found vulnerabilities in their code at work, similar to the ones in the challenges. In our most recent workshops, developers had to leave <em>during</em> the workshop as they realised the code they were running in production was vulnerable.</p><p>Either now or in the future, we’re willing to bet that developers you send to the workshop will use what they learn to fix security bugs you have in production today.</p><h4><strong>Your developers will spend an entire day improving their skills</strong></h4><p>Finding time for training is difficult. Even if you have “20%” time, it’s hard to decide what and how to focus your efforts to increase the quality of the software that a developer produces.</p><p>Security is not the only measure of software quality, but it is an important one. By taking our workshop, your developers have an excuse to spend an entire day learning and thinking about security.</p><p>Many attendees are mentally exhausted by the end of it and so don’t stick around for the after-workshop dinner and drinks. There’s no version of this story where they complete the workshop and learn nothing of value.</p><p>This is good for the developer. It increases the quality of the software they produce on an axis that is massively important to users, to you, and to the general public.</p><p>This is good for you as their lead or employer. It signals that you care both about the security of the software that you’re creating <em>and</em> about the long term career prospects of developers on your team.</p><h4><strong>Many other teams have put their developers through the workshop</strong></h4><p>We’re not suggesting that you should do things just because other people do them.</p><p>We are saying that other teams have sent developers to the workshop and have left us overwhelmingly good feedback. This might be construed as evidence that the workshop will be worth it for your developers too.</p><p>We’ve run the workshop for developers at <a href="https://www.new-bamboo.co.uk/blog/2015/03/02/building_secure_web_applications_with_ruby_on_rails/">New Bamboo</a>, <a href="https://www.digital-science.com/">Digital Science</a>, and the <a href="https://www.gov.uk/government/organisations/ministry-of-justice">Ministry of Justice</a>. <a href="http://www.lonelyplanet.com/">Lonely Planet</a>, <a href="https://www.futurelearn.com/">Future Learn</a>, <a href="https://www.reevoo.com/">Reevoo</a>, <a href="http://wearefriday.com/">Friday</a>, <a href="https://www.mysociety.org/">My Society</a>, <a href="http://paymentcardsolutions.co.uk/">Payment Card solutions</a>, and many other companies have sent developers to our public workshops. We’re also the <em>de facto</em> security advisors for a number of startups and small businesses that seem to be happy with our services.</p><h4><strong>That’s all</strong></h4><p>As a former developer, I’m hesitant to make claims about any of our offerings that I can’t back with evidence. I’m as allergic to sleazy sales pitches as you are. I’ve tried to lay out some reasons why our workshop will be valuable for you and your developers, based primarily on the feedback we’ve received from past attendees.</p><p>Some developers find the workshop too easy, others impossibly hard. We’ve tried to address that by adding multiple levels of hints and challenges of varying difficulty. Most developers find it just challenging enough that they complete about 80% of the exercises in time.</p><p>At this stage, based on past feedback, I’m willing to bet that our workshop is probably good. There’s not much more I can say to convince you of that.</p><p>If it sounds like something you’d like to run for your team then please get in touch at <a href="/service/mailto:ali@happybearsoftware.com">ali@happybearsoftware.com</a>. If you’d instead like to send developers to the next public workshop, tickets are available here: <a href="https://ti.to/bearclaw/rails-security-workshop-september-2017">https://ti.to/bearclaw/rails-security-workshop-september-2017</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=665f0ef79327" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bear-claw/why-you-should-send-your-developers-to-our-security-workshop-665f0ef79327">Why you should send your developers to our security workshop</a> was originally published in <a href="https://medium.com/bear-claw">Bearclaw</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Black Cube]]></title>
            <link>https://medium.com/@alinajaf/the-black-cube-fe87319ad111?source=rss-36a609325382------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe87319ad111</guid>
            <dc:creator><![CDATA[Najaf Ali]]></dc:creator>
            <pubDate>Sat, 23 Jul 2016 22:54:41 GMT</pubDate>
            <atom:updated>2016-07-23T23:04:35.946Z</atom:updated>
            <content:encoded><![CDATA[<p>The entity is all-knowing, all-watching. It exists outside of space and time, everywhere and everywhen. It sees everything you have done, and knows everything you will do.</p><p>The centre of the world is the cube. You always know its direction from where you are. The reason you learn the points of the compass are so that you can use one to orient yourself to it. Millions of humans across Earth whisper words they don’t understand in it’s direction every day.</p><p>We had the windows down in the taxi on the way in to the holy city. A sign in the desert on the way in read “believers only from this point onwards”. We had our documentation checked on the way in.</p><p>“As a believer, you’ll know when you see the sacred temple” my mother said. “You’ll feel it in your heart, there it is” she said, as she pointed to the just-visible towers in the windshield of the taxi.</p><p>I saw the towers. I might have felt something.</p><p>We stayed in a hotel close to the sacred temple. There was a McDonalds at the bottom floor. You could look upon the house of the entity while chowing down on a fillet-o-fish value meal.</p><p>If the entity exists outside of time, could I be punished for something I haven’t done yet? Could I be rewarded for some good deed I’m yet to do? Perhaps something horrible will happen to me to make up for me being born to a good family?</p><p>I was excited, and nervous to see the cube. I didn’t know what to expect. I didn’t know what was inside. I did know that a rock that fell from heaven was housed next to it. I wanted to see this rock, and touch it if I could get the chance.</p><p>We visited the sacred temple on a quiet day, so we could get quite close to the cube. This was more out of laziness than piety. The rites called for walking around the cube seven times. The closer we were to the cube, the shorter each walk around it would be.</p><p>The cube had a crowd of a few hundred people around it, tightly packed against it, moving slowly in a circle around it. We joined this crowd. Men wore the customary two towels, and women were covered head to foot in black. Elderly pilgrims of some wealth were carried around the cube in palanquins by teams of men.</p><p>We moved into the crowd and became a part of it. It smelled like sweat, miswak, and cologne. I was holding my sisters hand on one side and my mothers on the other. This struck me as sub-optimal. If I lost my mother then the two of us would be alone. If I lost my sister then… well that didn’t bare thinking about.</p><p>Pushed along by the crowd we completed a few circuits and said the words. I was hit in the head by one of the palanquin handles twice. We were still together, though there had been a few moments where the crowd had put us out of view of each other.</p><p>The floor of the sacred temple is marble. Moving in a densely packed crowd means you’re shuffling more than you are walking. I was surprised to feel something like an arm or a leg under my foot. I stopped and looked down.</p><p>An ageless woman looked up. I don’t remember her face. In my dreams she never has her own face. She takes someone else’s. She says some words to me that I don’t understand. It may have been some dialect of Arabic. Her skin was dark, so maybe somewhere from South India. Perhaps Sri Lanka? Maybe East Africa? I had no idea. She was disabled, perhaps with polio or some kind of spinal injury that meant she couldn’t walk. She was trying to drag herself around the cube.</p><p>She was being crushed by the swirling throng. By me, by my sister, by my parents, by the palanquin teams trying to get their charges off their backs as quickly as possible, by all the believers from all walks of life who’d come to the sacred temple today to perform the rites.</p><p>We had locked eyes. I didn’t know what to do. I had to keep moving. I had to keep my sisters hand or she would be lost to the crowd. There was no way for me to help her.</p><p>We went around again a few more times. I didn’t see her again. On the last circuit I stepped on something. It was some bloody combination of flesh and bone fragment, crunching and tearing beneath me.</p><p>Later I would ask my family about the woman.</p><p>“Some disabled people come to the cube to pray for a better life” my mother said.</p><p>“She was worthless, she did the right thing by ending her life here” someone else said. “Now at least she has guaranteed her place in heaven”.</p><p>Afterwards, or before, we were encamped in the desert, five kilometres to the East of the holy city. The encampment was in a valley surrounded by mountains. There were thousands of large, white tents, neatly arranged in rows. It was cool at night and blistering hot in the day.</p><p>On our first night, the sky was filled with stars. This was one the few moments in my life where I’d see a sky so full with the cosmos. I remember thinking that this was the same sky the messenger would have seen fourteen hundred years ago.</p><p>The encampment was filled with pilgrims from across the world. The group we travelled with had a few of my father’s friends from university, and some other people we didn’t know.</p><p>On one day the men from our group sat in a tent for hours talking. It was mostly in languages that I couldn’t understand. Some Arabic, some Sindhi, and a bit of Urdu from what I could tell. Many of the men cried, my father included.</p><p>A few days into our stay, word spread that there was a fire. We didn’t know where it was and whether we should be concerned. Over the next few hours panic spread, and people had started leaving their tents and walking back towards the holy city.</p><p>We left our tent too, with nothing but the belongings we could carry in our hands. The pilgrimage called for men to wear clothes without seams, so pockets unfortunately weren’t an option.</p><p>The wind was hot. We could hear steady stream of popping noises in the distance. These were gas cylinders exploding. Tents were catching fire, and the fire was spreading towards us quickly. We were on the road heading back towards the holy city, with tents stretching out to the horizon on each side. The popping noises turned to deep, pounding thuds. More and more of the tents around us caught fire.</p><p>My mother, father, sister, and I were together. We tried to find people from our group and told them we would walk back. If we had stayed any longer though the fire would get ahead of us on both sides.</p><p>The entrance to the encampment was a tunnel through the mountains. We would have to walk <em>through</em> the tunnel to leave the encampment. This would be perfectly safe at any other time, but right now five million pilgrims were fleeing for their lives. It was either certain death by flaming inferno or possible death by stampede.</p><p>We walked through the tunnel. Some of the crowd started running. We held hands in a chain, walked steadily, and kept going until we found ourselves on the other side of the tunnel. An older man in our group had made the journey barefoot. His feet were covered in blood when we met him on the other side. He had to be carried the rest of the way.</p><p>Later we would learn that there was in fact a lethal stampede in the tunnel, but we had missed it by about twenty minutes.</p><p>A coach arrived to pick up our group and shuttle us to apartments in the holy city. We were living about ten people to a room, but we were safe.</p><p>That night I saw the woman in a dream. This time she’s speaking English. She looks up at me and tells me that I should have helped her.</p><p>I woke up and I knew that the entity had chosen me to help that woman that day. That was why our eyes met. It was a test for <em>me</em>. I could have said or done something to help her. I had failed the test, and this dream would always remind me of it.</p><p>Official reports stated that no more than a few hundred people had died in the incident. No reasonable person could stand on the highway between the tents in that fire and believe so low a figure. Unofficially, two thousand people were reported “missing” in the fire and the resulting stampede.</p><p>I felt ill as I heard the news. Was this my fault? Was this punishment for how I had failed to help the woman so close to the cube? Was this punishment for <em>everyone</em> who had failed to help her? Had I failed the only test, the only direct communication that the entity had ever made with me?</p><p>I have the dream once or twice a year.</p><p>Sometimes it’s just me and the lady in the sacred temple. I’m stuck further away from the cube, she drags herself around it and I have to watch.</p><p>Sometimes she’s able-bodied, and it’s her hand I’m holding as we walk through the crowd.</p><p>In the worst version of the dream her eyes are black and she’s shouting at me in a deep, guttural voice. Her words are unintelligible, but she’s angry, and I know she thinks her predicament is my fault.</p><p>Sometimes the dream is a replay of the events. Only that she takes the face of one of my aunts, or a servant from my childhood.</p><p>The black cube always sits in the centre.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe87319ad111" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Choose your own adventure]]></title>
            <link>https://medium.com/@alinajaf/choose-your-own-adventure-e282318a1817?source=rss-36a609325382------2</link>
            <guid isPermaLink="false">https://medium.com/p/e282318a1817</guid>
            <category><![CDATA[racism]]></category>
            <category><![CDATA[virtue-signalling]]></category>
            <dc:creator><![CDATA[Najaf Ali]]></dc:creator>
            <pubDate>Wed, 13 Jul 2016 23:09:03 GMT</pubDate>
            <atom:updated>2016-07-14T09:09:15.050Z</atom:updated>
            <content:encoded><![CDATA[<p>The hard steel of a car slams into you. You hear a crunch. You’re on the asphalt. You’re bleeding, there’s bone fragment sticking out of your leg. The driver speeds into the distance.</p><p>You cry out for help. Moments later a meritocracy of straight white men materialises from the ether. They begin their work.</p><p>“Overall, injuries related to automobile accidents have decreased over the past decade”, the first one says. You’re shaking.</p><p>“It doesn’t seem that bad, you’re overreacting. You should be thankful to the driver for not causing more serious injuries. Traffic accidents used to be much worse”, the next one says. You look on, incredulous.</p><p>“Are you sure you want me to call an ambulance and get the authorities involved? You’re going to ruin the poor drivers driving career.”, the next one says. You want this to be a nightmare. You want to wake up now.</p><p>“Look at this everyone, zero points on my license, I’ve never hit anyone in my life”, one says to the others. “Some of my best friends are pedestrians!” he declares. “One time, I met a bad driver, and told him to his face that he had no place behind the wheel!” His fellow straight white men of self-declared good driving ability place a garland of roses around his neck. He takes his place atop a gilded palanquin, and they carry him on their shoulders.</p><p>“Saying that someone is a bad driver isn’t helping. If you want people to change, you can’t start by insulting them” says another. The agony you’re in is now superseded by dumbfounded bewilderment.</p><p>“Don’t you dare think about leaving places with bad drivers. Otherwise, how will you make them better? You need to expose yourself to as many accidents as possible to make our roads safer”, another proclaims. You lose consciousness.</p><p>You begin to hallucinate. An atemporal dragon performs a Fourier transform of your ring finger. You can’t decide your favourite song, so your favourite doorbell decides for you. Reality falls apart and recomposes itself at semi-regular intervals marked on an advent calendar with contour lines of brownian motion at each door.</p><p>What happens next though is <em>completely unbelievable</em>.</p><p>Someone looks down on you, worried. They decide to take action. <em>They ask you if you’re OK</em>. You’re obviously not OK, but you appreciate someone finally asking. They call you an ambulance, because it’s the only thing they know to do. They wait with you until the ambulance arrives. You manage to unlock your phone and indicate who to contact, so they get them on the phone and explain the situation. They’re clearly distraught themselves but try their best to calm you down and make you feel safe.</p><p>You get hit by a car every year or so. You’re worried because drivers are getting more reckless, and more people you know are getting hit by cars more often. Your children were both hit by cars <em>in the womb</em>. That they will also be hit by cars every year fills you with sadness.</p><p>You decide not to bring up car accidents with straight white men, especially ones that like to make a big show of their good driving ability. When they see the casts and bandages on you though, they start talking about their long careers of good driving and how much they hate bad drivers. This exasperates you, so you politely try to change the subject when it happens.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e282318a1817" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>