Native vs Hybrid apps are two different ways of writing your mobile application. Woodridge may use either depending on the type of your application, your risk tolerance of depending on a framework, and how much native functionality you need.
By Chad Eatman
The title of this blog should frighten most developers. Generally speaking, we want to avoid running a SQL statement – UPDATE, INSERT, or DELETE – on production if it possible. One statement can do a lot of damage if it’s not 100% correct.
By Henry Dau
Writing code is easy to today’s world. I’m not even talking about writing quality code, following the Agile manifesto, nor eeking out every possible nanosecond of speed out of your code. I’m talking about punching keys and having having text appear on the screen.
By Lorenzo Gallegos
As technology continues to rapidly evolve, it seems like hackers’ methods of attacking modern software are evolving at an even faster pace. Unfortunately, the average software developer has little to no understanding of the miscellaneous attacks that are used by hackers, nor do they completely understand how to help prevent them.
By Chad Eatman
“Should I invest time learning a new software tool? Or, should I just build my own?” These are questions I encounter regularly as a software developer, but these questions are also relevant to any individual or company trying to make their business more efficient.
By Jennifer McAdams
Woodridge is proud to announce that we have been named a winner in the 2018 Denver Business Journal Best Places…
By Jennifer McAdams
Woodridge is proud to announce that we have been named a winner in the 2018 Colorado Companies to Watch competition….
By Kaj Gronholm
Taking the dive into creating custom software for your business is not a small decision. Whether it’s creating a new app or adding features to an existing one, you could be looking at $10K, $100K or even $1M dollars in costs. There’s no reason to ever make that decision unless you will get at least that much in return.
By Henry Dau
Functional programming is a foreign concept to many software developers. Sure, they may have heard of functional programming before, maybe even seen a language or two, but imperative programming is still their bread and butter. In this day and age, a purely functional language is only useful for heating your computer (for most purposes), but knowing functional programming concepts can be immensely beneficial.
By Lorenzo Gallegos
At Woodridge, we encounter a variety of codebases. These codebases consist of code we write as well as code that we inherit. In the event that the original developers retire or pass away, we simply inherit the code. On the other hand, we inherit code from prospective clients where the code is less friendly to work with.
By Kaj Gronholm
iOS 11 was recently released and that means two things: One, your iPhone just got some very cool new features and two, your apps might break.
By Tyler Bank
Have you considered building a mobile app, or perhaps you have the beginnings of a great idea? Regardless, you’ll have an important decision to make, “Should my app development team build a native or hybrid app?” There are several variables to consider: the initial app launch time, the budget for the app, the app’s complexity, and post Minimum Viable Product (MVP) desires.
Bbashash is a command line shell, and a Bash script is a set of instructions within the shell. The terminal, or command line, is an interface where text commands are executed.
By Lorenzo Gallegos
It seems like every day we hear about another security breach in the news. From Target to Ashley Madison, it seems like everyone is a target nowadays (no pun intended). So how do we protect ourselves? The first steps are awareness and education, but specifically for software developers, you must learn to think like an attacker, and in order to think like an attacker, you must learn how security breaches occur.
By Chad Eatman
Maintaining code and appearance for your web app across multiple browsers is not always trivial. Different browsers may only implement certain features and sometimes different browsers will implement the same feature differently. You want to support as many users as possible, but doing so can increase development costs. So how do you choose which browsers you need to support?