Panorama Education’s (YC S13) Git Workflow

As happy git users, we love learning how other people use our favorite version control system. So, we thought we’d add to the discussion and share how we use git and other tools to drive our engineering work. We’ve been improving our git workflow for a few years, and our current solution is optimized around:
Easing work parallelization
Communicating who’s working on what
Allowing us to prioritize tasks
Allowing external stakeholders to view task progress
Preventing us from deploying un-QA’d code
Creating a clear path for engineers to take their tasks through the pipeline of development, testing, QA, all the way to production without blocking on work from others
We’ve been pretty satisfied with our setup – check it out, and let us know what you think!

Task Management
For task management, we use JIRA, both for its flexibility in configuration and because using different components of the Atlassian ecosystem together gives us some nice benefits (more on that below).


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/TIrUQNJ9OO4/

Original article

Is Model-View-Controller dead on the front end?

More and more front-end developers are adopting unidirectional architectures. So what’s the future for the classic Model-View-Controller (MVC) approach?In order to understand how we got to this point, let’s first review the evolution of front-end architecture.Over the past four years, I’ve worked on a great deal of web projects and spent a good amount of time architecting front ends and integrating framework into them.Before 2010, JavaScript — that programming language jQuery was written in — was used mostly for adding DOM manipulation to traditional websites. Developers didn’t seem to care much about the architecture itself. Things like the revealing module pattern were good enough to structure our codebases around.Our current discussion of front-end vs back-end architecture only came about in late 2010. This is when developers started taking the concept of a single page application seriously. This is also when frameworks like Backbone and Knockout started to become popular.Since many of the principles these


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/QyFvOp_n2D4/is-mvc-dead-for-the-frontend-35b4d1fe39ec

Original article

Qt for Go which supports Windows/macOS/Linux/Android/iOS/SailfishOS/RaspberryPi

README.md

Overview

Qt is a cross-platform application framework.

Go (often referred to as golang) is a free and open source programming language created at Google.

This binding aims to make it as simple as possible to write applications for all operating systems supported by Qt in Go.

The project is pretty much a WIP and not recommended to be used in production yet.

However it should already contain everything you need to build fully featured Qt applications in Go.

Screenshots of the Line Edits example

Installation

Full or stub installation?

The full installation requires at least 8gb free ram and takes 20 min.

The stub installation requires only 1gb free ram and takes 10 min. (experimental)

The only differnce between those two version is, that you won’t be able to use go run/build to build your applications if you choose to install the stub version.
You are therefore limited to the use of qtdeploy to build your application.

To build


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/g9M0W2afexI/qt

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: