I recently participated in a few hackathons and hack nights this year. They are a great experience for developing a lot of interesting ideas in a short amount of times. It’s extremely rewarding to get a product out the door over a weekend, or even a night.
Some companies have made hackathons feel extremely exploitative. They’ll stuff a bunch of developers in a room, with free pizza and some prizes and they get to keep the results of your work.
The next time you see an interesting event to participate in, please consider these in mind.
Find a hackathon that put you first
Choose the ones that support your rights. We work hard for our projects, and they belong to us. A lot of issues arise due to some of these problems
Talk with your Local meetups and user groups for recommendations
Each of the ones I chose to participate had the following criteria:
The participant keeps all rights to the code they produce
The event has been vetted out by credible people with a good track record of support.
Finding a credible event can be difficult. Talk with your Local meetups and user groups for recommendations. In Orlando, we have a few tech advocates that go out of their way to check on these.
Once you find a decent hackathon that would benefit you, it’s time to prepare yourself!
Have a goal in mind
Having achievable expectations allows us to feel successful at these events.
Fellow hackathon team member Mick Musak recommended to set my expectations at the start the Hack the Arena event.
I chose a goal of just completing an app, and learned a bit more about how Web Sockets worked in Node.js.
Keeps your mind grounded
At the Hack the Arena event, there were multiple groups that had similar ideas. Our idea of a digital light scheme was done on a hardware level, and I felt eclipsed. I messed up on the presentation, and felt really embarrassed.
Seeing that I was upset, Team members, Mick and Tim, told me their goals were fulfilled. They were proud to participate, and was happy to have the project on their githubs.
By setting the expectation, they were satisfied.
Here’s a compilation list of my goals at the past hackathons
Learn React Native
Build a small fun game that I would play
Create an Android App
Don’t freak out when presenting the idea
Get a T-Shirt
Use your B-tier ideas
If you have concerns about being exploited for your brilliance and hard work, I have a great idea, well, a mediocre idea.
Save the best ideas for yourself, and use one of the throwaway ideas.
You’re a person who can come up with a bunch of ideas, and they’re cheap to think up. It’s the implementation that takes effort.
Leave enough for the imagination
Some may disagree with this idea, and that’s okay.
Use the Throwaway Jokes
I use my time at Hackathons to learn new things, or build a slightly interesting idea. This reduces the amount of personal risk to my ego when my awesome idea gets shot down due to poor execution.
This is where I pull out a list of joke ideas. In fact, a few local winners of hackathons have won with an X for Y product clone. These ideas are great for learning new tech.
Build for your audience
It’s really easy to try to do everything in a project for the hackathon. When we plan on a regular project, we try to get all the different features needed for the idea to work. On a time constraint, a lot of features are unnecessary.
Presentation Oriented Design
Many of the projects available relies on having the 3-5 minutes to present your project. Spend a fair amount of time designing what the screens would look like, and the basic flow of the idea.
This allows us to skip certain ‘crucial’ elements of an application, like authentication, or server communications.
Time is the ultimate enemy
Plan on creating the smallest MVP you can imagine, then make it smaller. Depending on the time of the hackathon, a lot of items are unnecessary.
Reduce the scope just enough to get your point across
OAuth2 Social Media Authentication for an instagram clone, don’t need it.
An entire backend server to process data, you might not need it.
On projects where I’m learning something completely fresh, or a lot of members with little experience, I want something super small and simple.
You’ll want to reduce the scope just enough to get your point across.
Keep your heart light
Tensions get high for competitors, trying to push out an idea as soon as possible. Remember to laugh, and believe that people are doing their best.
When it came time to setup deploys for our AngularJS application, we had a few areas in our Services that had hard-coded API keys into the application. A lot of guides online have different ways of incorporating ng-constant into the build process. At Fresh Lines, I work on a lot of server-side projects. I’m comfortable with a standard convention for my configurations, like a /config folder to store environment based settings.
This particular setup is based on onefootball’s guide, and mirrors closely to how some server side frameworks have handled their environmental variables.
I want to have a nice config file, that lists all my environment specific settings, like
and in config.production.json.
then have the ability to inject the configuration into places where I need it.
The project folders would be set up so that we have a separate config folder to hold all of the private information:
In this config folder, we’ll have the following files. These files represent the different environments we want.
Install grunt-ng-constant and lodash to your local project directory
(optional) If you’re using grunt-jit: Add grunt-ng-constants to your grunt-jit.
We need to Add the Configuration JSON files to the Gruntfile. Add these lines to your Gruntfile.js. This should be at or near the top of the file. If you’re Gruntfile is not at the root of your project, adjust conf1 and conf2 to match. lodash is included to merge both JSON files together
Add the following grunt task inside your grunt.initConfig. This sets up the configurations to read the buildConfig and set it to an ENV file.
Replace the dest: path with you keep your scripts in your project. I only have a production and development environment.
Finally, in the build and serve tasks of Grunt, we’ll need to call ngconstant to our setup. grunt build is for production, and grunt serve for development. I would add this task as the first or second task to be run
And for grunt serve
Then for every module where you would use this, include config as a dependency, and inject ENV
So I’m sitting in a trampoline recreation center for my sister’s party. Chaperoning and Chaffeuring around. With some downtime, and not in the physical fitness to jump around, it felt like a good time to pull out the laptop to work on some side projects.
At a few of these places, they offer guest networks as a common courtesy. Unfortunately, some of the free WI-FI connections aren’t that great, and I could not get a solid connection. What’s a guy to do?
In periods of network downtime, here are a few things I have done to feel slightly more productive.
Program by Guessing.
How many times have you tried this? Picking up a new programming language, or framework, we let the IDE and it’s QuickStart be our guide. Whenever I come from a language that’s similar, I do a little divination, programming by guessing at what the method names or standard library names are. Sometimes we can get lucky.This time was not one of those times.
I’m pretty new to Android Development. For the short time I was without internet, I was thinking of doing something simple. I opened up a few template projects, and played with wiring up the different templates together. Android Studios’ UI Builder was a definite good use of my time.
I’m sure a lot of you have done this before. I opened up an Android Project through Android Studio, and started relying on AutoCompletes. I did rely on hitting Firebase for my application, and without access to the network, I started a little service of my own. I’m pretty comfortable with Rails, so I created a small API Service and routed the firebase urls to my localhost.
There’s probably not enough test coverage when we’re building our personal projects. Some form of test coverage would be great to do.
Future-Proof solution. Download it now!
While doing a little research, I came across devdocs.
I recently picked up a small project over the weekend. With the promise to myself to launch an MVP by week’s end, I needed to have a solid system down that worked well enough.
It is a customer rewards tracking system, so that a business can keep track of customer purchases, and offer discounts at time of purchase. This is meant to replace their current Access database.
Tickets and feature management is a must. I’ve tried other ticketing systems, and I wanted a little more integration with Github or Bitbucket. From a recommendation from my coworker Brandon, waffle.io has been a very good choice. Tickets integrated well with Github issues, features, and pull requests. Progress of the ticket was tracked as I pushed changes to feature branches.
Some required features to emulate the current system:
Cashier can add a new customer into system
Cashier can add a visit and add a new reward
A report to determine when customers at the month are
Some new features requested:
Rewards to show up at intervals of dollars spent
Rewards for frequency of visits
Alerting the cashier at time of entry about the available deal.
Make sure it works
Since this is a part time project, I need to make sure that it’s functional enough for people to use. While I’m doing some things from a TDD perspective, I didn’t want to spend too much time debugging launches.
There were some growing pains setting up Capistrano to deploy on my own servers. I wrote up some steps and left it in my project’s readmes. Overall I’m pretty satisfied on how it works.
Keeping it small and tight.
I don’t want to mess around with small details, like User Authentication and Authorization. Using gems like CanCanCan and Devise speed up my creation process.
How do we find relevance in learning new programming stacks? How do we remain relevant in our understanding of web architecture? New frameworks rise and fall faster than a prime-time lineup. Wheels are reinvented faster than we can put them on cars!
When I’m doing things by myself or at my job, I want to get it done. I’ve developed habits to avoid using new / exciting / untested stuff for production. I also avoid rolling my own…anything. For the client, and for anyone else down the line, maintenance can be more expensive and mentally tasking. They want a working awesome product.
Coming up with new projects, I don’t imagine the minor (but important) details of my stack. I’m more interested in the end product. Architecting out a solution, drawing out my tables and relations, these are the parts I enjoy. My standard set of tools: Laravel / Rails, MySQL, Bootstrap, Nginx. Anything that gets it rolling out the door.
For me, it was the fear of failing to understand. After programming for a while, there was a certain comfort in knowing that things worked the way you expected them to work. Switching may take me a lot longer to learn, and cause me problems in getting what I want.
Life is hectic, and stressful. Programming is safe. It’s my sandbox.
Improving creative morale
I had a strange week filled with visits to the cinema. I thought of a game regarding movie earnings and Adam Sandler. Given a Movie title and the budget, provided by BoxOfficeMojo, the player had to guess the gross earnings.
Jackbox.tv’s online game model of an online sign-in and streaming looked amazing. I love the idea of a client-server game sessions, and the ease of sign-in. The interface is pretty slick. I want something like that.
Some of my other friends would take this idea, and form a medium-sized team where a lot of people do very little. Maybe make a Kickstarter from it. This is a silly prototype, and something that I want. So I started building.
It’s still not done yet. But the passion of creation is back.
When building is not enough
Meeting other people who appear passionate about the craft reminds me of why I started in the first place. I came to this industry since the challenge exists. While programming can be a solitary activity, we have a community full of supportive, brash, intelligent developers that can help.
Help a newbie
Working in coffee shops for the past few months, I met a few ‘up-and-coming’ developers. I’m not too sure what that means, but these kinds of people are extremely hungry and passionate about new stuff.
Encouraging their growth and development brings all the warm fuzzies into me. They show me their projects. I love seeing them. While I don’t have any pretty things to show yet, I have my favorite tools. I love showing off Github Pages and setting up their machines for Jekyll. Demonstrating the power of Virtual Machines and how easy it is for them to get a development environment setup so they can try out a new language or node.js tool. Or even helping them debug a current problem.
Contributing to Open Source
There are a few tools that I like to use, but documentation can be kind of scarce until I learned how to use it. Reading through open source code for fun may not be the first thing I went to, but helping to fix a bug that I ran into time and again helped.
Join a meetup
In college, I remember meeting with people of like minds, going through a similar trials and tribulations of finishing school work. I’m not used to meeting with other people with the same job title I have. Meeting up and Talking with others of like minds helps.