Tag: back-end developers
Web development has come a long way since 2004, the year Vineyard put his first website into production. Hehad been learning about programming for a while, but he didn’t understand the steps he needed to take next. Vineyard says he had almost no context for getting a programming language to work. Best of all, he was programming PHP in Dreamweaver on Windows XP (yeah, baby!). The work he does today is drastically different from the work he was doing then. Vineyard utilizes tools like virtual machines, command line utilities, pre-processors, and package managers. How did he get here? How do others get here? In this session Vineyard will tell you about the journey he's taken to becoming a self-taught, professional PHP web developer and give you hints on where he thinks the web development industry is going next. He will highlight the use of DevOps and testing, future frameworks and tools, and statements from thought leaders. From a leadership perspective, too, he'll talk about how to keep your co-workers and followers from making the same mistakes he made. Vineyard will also give tips on how to encourage their personal growth into the awesome world of web development.
Such Node.js, much happy, wow! You might think that Node.js is a newcomer in town, but it has been around for for about 5 years now! Very prominent companies such as LinkedIn, Paypal, Walmart, and Yahoo! have adopted Node.js and are paving the way for it to become the next major platform. Node.js will make your developers happy and your Rails, PHP and Java developers jealous. Node.js is quickly becoming a highly performing, efficiently coded, happy-developer platform and it fits right into the Higher Ed community. This talk will explore the advantages of using Node.js in Higher Ed. We’ll discuss several use-cases ranging from powering a mobile application to a full-blown web application and how to start the conversation to start using Node.js! Getting started is easy and the power of the Node.js community shines a light on the endless possibilities.
We generate lots of content and manage lots of data in disconnected ways. The University of Arkansas started a project a few years ago called the Campus Data Project. A not seksi name for an incredible foundation with a REST API that lets users tie all kinds of data together that they never could before. From campus maps crossed with the campus directory to a news platform that updates experts lists and research blogs, the team has an ecosystem of useful reusable information getting more valuable with every piece of content added to it. Nixon will talk about the evolution of this system, how we use it currently, what our future plans are and how we have shared this platform with others in our state.
It's possible to make a structured, consistent, API that can handle changes to logic and the schema. Sure, it seems like a good plan to dump everything out of the database today, but what are you going to do when something changes down the road? Let's have a talk about some SOLID ways to structure our APIs and keep them from breaking down the road.
Less than two years ago, the largest department at Carnegie Mellon University ran a student database off defunct software, required students to complete forms by hand and collected qualifying exam documents from 25-35 students each semester via email. Since then, the university has updated its student database, built a department-wide data warehouse, introduced interactive forms and created a cloud-like solution for qualifying exam document collection. The key to these improvements has been the fruitful working relationships between academic advisors and technical staff. This presentation will provide an overview of how the presenters framed and prioritized IT requests, partnered with IT staff to make small and large-scale projects come to fruition and gained support in new IT initiatives. They will address the challenges of communicating across domains of expertise to successfully implement new technology solutions from both a higher education and IT perspective.
Data driven applications have been the norm for years, yet the availability of university data is often lacking. Many of our universities’ data is locked up within departmental silos and closed systems. Our requests to access this data usually result in blank stares, laughter, or confrontation. After all, it’s “my data”! And all the while our applications aren’t as robust as they could be, and users have suffered. At The Ohio State University their campus mobile app has been a cross-departmental collaboration, aggregating lots of campus data. Other departments have begun to see this as a model to follow. Building on this success, OSU launched its Enterprise Integration Platform initiative. The goal is for all campus data to be available via web services/APIs primarily RESTful accompanied by a user friendly searchable API where any person on campus can easily find data available and request access. It will give developers the ability to create robust applications that extend far beyond the silos that fall within their departments. This is a technical change as well as it is a cultural one. Developers can create the applications their departments are asking for. It also creates an awareness of the collective capital that resides in campus data. We’ll share our wins, losses, challenges, and long term plans. We’ll describe the technologies we’re using and things we’d do differently.