- KPI dashboard review
- Since our last retro, what's gone well?
- How do we feel about our productivity and work/life balance
- How is the product better than last week?
- How is the company better than last week?
- Is there anything we should ask a consultant about?
- How is the office/ops?
- How can we enjoy the journey more?
module Logic | |
-- Connective is a fancy word for operator. | |
namespace Connectives | |
-- Truth: Also known as the "unit" type, (there is only one truth in value, | |
-- literally). | |
-- Scala: type Truth = Unit | |
-- Haskell: type Truth = () | |
Truth : Type |
// Simple example, but the idea holds for more complex objects. | |
/* 1) Start with OO */ | |
// user.js | |
class User { | |
constructor(firstName, lastName, email) { | |
this.firstName = firstName | |
this.lastName = lastName |
// convert 0..255 R,G,B values to binary string | |
RGBToBin = function(r,g,b){ | |
var bin = r << 16 | g << 8 | b; | |
return (function(h){ | |
return new Array(25-h.length).join("0")+h | |
})(bin.toString(2)) | |
} | |
// convert 0..255 R,G,B values to a hexidecimal color string | |
RGBToHex = function(r,g,b){ |
#Understanding MVC And MVP (For JavaScript & Backbone Developers)
Before exploring any JavaScript frameworks that assist in structuring applications, it can be useful to gain a basic understanding of architectural design patterns. Design patterns are proven solutions to common development problems and can suggest structural paradigms to help guide us in adding some organization to our application.
I think patterns are exciting as they're effectively a grass roots effort that build upon the collective experience of skilled developers who have previously faced similar problems as we do now. Although developers 10 or 20 years ago may not have been using the same programming languages for implementing patterns, there are many lessons we can learn from their efforts.
In this section, we're going to review two popular patterns - MVC and MVP. The context of our exploration will be how these patterns are related to the popular JavaScript framework Backbone.js, which will be explored in greater detail later on.
Author unknown. | |
1.) Algorithm Complexity: You need to know Big-O. If you struggle with | |
basic big-O complexity analysis, then you are almost guaranteed not to | |
get hired. | |
For more information on Algorithms you can visit: | |
http://www.topcoder.com/tc?module=Static&d1=tutorials&d2=alg_index | |
2.) Coding: You should know at least one programming language really | |
well, and it should preferably be C++ or Java. C# is OK too, since |
// Async/Await requirements: Latest Chrome/FF browser or Babel: https://babeljs.io/docs/plugins/transform-async-to-generator/ | |
// Fetch requirements: Latest Chrome/FF browser or Github fetch polyfill: https://github.com/github/fetch | |
// async function | |
async function fetchAsync () { | |
// await response of fetch call | |
let response = await fetch('https://api.github.com'); | |
// only proceed once promise is resolved | |
let data = await response.json(); | |
// only proceed once second promise is resolved |
- x : not worked
- o: worked (able to open in quicktime but need conversion)
- oo: worked well (preview worked but wrong aspect ratio)
- ooo: worked very well (preview worked, and aspect ratio’s right)
(Codecs are extracted from https://web.archive.org/web/20120722124832/http://opencv.willowgarage.com/wiki/QuickTimeCodecs )