2014 Summer of Extreme Design-Build - Revision history

Marcin at 18:13, 13 June 2018

2018-06-13T18:13:51Z

← Older revision		Revision as of 18:13, 13 June 2018
Line 1:		Line 1:
			<html><img src="https://docs.google.com/drawings/d/e/2PACX-1vQuAWe_gd_luG3ac0YzoOvG1sF-f9T3DFy4Mq5nAGVCGKVlgPoyfMzHvQBcWTx2xl-hOwRYYaBH4oDp/pub?w=816&h=1056"></html>

			[https://docs.google.com/drawings/d/1TPEo0Iqz5B5a68AHsDkdFFurEdPt8dxt92PgCHtrvgQ/edit edit]

	=Introduction=		=Introduction=

Jorgeandr3s: /* Learning Objectives */

2014-06-05T15:41:24Z

Learning Objectives

← Older revision		Revision as of 15:41, 5 June 2014
Line 83:		Line 83:
	=Learning Objectives=		=Learning Objectives=
	By the time you leave the 3 month program, you will:		By the time you leave the 3 month program, you will:
	*Be able to design homes in Sketchup and interiors in [[MySweetHome3D]] (by jumping into user-friendly MySweetHome3D and massaging imported parts libraries in Sketchup). Part of the work in the summer will be based on generating component libraries for the Microhouse - as a construction set for regenerative housing.		*Be able to design homes in Sketchup and interiors in [http://www.sweethome3d.com/ MySweetHome3D] (by jumping into user-friendly MySweetHome3D and massaging imported parts libraries in Sketchup). Part of the work in the summer will be based on generating component libraries for the Microhouse - as a construction set for regenerative housing.
	*Be able to design tractors - using parts libraries and simple design rules. These libraries will be generated throughout the summer, and the design rules follow basic principles of mechanical engineering.		*Be able to design tractors - using parts libraries and simple design rules. These libraries will be generated throughout the summer, and the design rules follow basic principles of mechanical engineering.
	*Be able to work on technical design file manipulation in CAD in FreeCAD and LibreCAD (power lies in simple tech design of LibreCAD, and ability to manipulate and import files from many formats). Interoperability is one of the key features allowing this project to go viral, so we will draw up and document techniques for file conversion.		*Be able to work on technical design file manipulation in CAD in FreeCAD and LibreCAD (power lies in simple tech design of LibreCAD, and ability to manipulate and import files from many formats). Interoperability is one of the key features allowing this project to go viral, so we will draw up and document techniques for file conversion.

Marcin: /* Introduction */

2014-05-23T02:55:55Z

Introduction

← Older revision		Revision as of 02:55, 23 May 2014
Line 1:		Line 1:
	=Introduction=		=Introduction=

	[[Image:summerxtreme.jpg~~\|600px~~]]		[[Image:summerxtreme.jpg]]

Marcin: /* Introduction */

2014-05-23T02:55:38Z

Introduction

← Older revision		Revision as of 02:55, 23 May 2014
Line 1:		Line 1:
	=Introduction=		=Introduction=

	[[Image:summerxtreme.jpg]]		[[Image:summerxtreme.jpg\|600px]]

Marcin: /* Introduction */

2014-05-23T02:54:43Z

Introduction

← Older revision		Revision as of 02:54, 23 May 2014
Line 1:		Line 1:
	=Introduction=		=Introduction=

			[[Image:summerxtreme.jpg]]


	OSE carries out most of its overall development at its headquarters - Factor e Farm - a 30 acre facility in the Kansas City area of Missouri.		OSE carries out most of its overall development at its headquarters - Factor e Farm - a 30 acre facility in the Kansas City area of Missouri.

Marcin: /* Links */

2014-05-22T04:23:21Z

Links

← Older revision		Revision as of 04:23, 22 May 2014
Line 113:		Line 113:
	*Read more about OSE's overall [[Development Process]].		*Read more about OSE's overall [[Development Process]].
	*See what we have for [[Students]]		*See what we have for [[Students]]
			*[[Summer of Extreme Design/Build Intro Survey]]

Marcin: /* Introduction */

2014-05-05T20:16:35Z

Introduction

← Older revision		Revision as of 20:16, 5 May 2014
Line 2:		Line 2:

	OSE carries out most of its overall development at its headquarters - Factor e Farm - a 30 acre facility in the Kansas City area of Missouri.		OSE carries out most of its overall development at its headquarters - Factor e Farm - a 30 acre facility in the Kansas City area of Missouri.

			Participants are selected based on an initial application and interview. The program cost is $450 per month, and includes food and dorm-style accommodations. People also have the option of camping out in our summer campground.

	Development happens most intensively during our Summer of Extreme Design/Build. In 2014, we will emphasize swarming – working with a group of 24 dedicated developers on a single machine or module design/build each week. In this way, rapid development and prototyping occurs on the time scale of a week – harnessing a weekly effort on the order of 1000 development hours. Areas include machine prototyping, infrastructure-building, and testing our machines in agriculture. Our summers are focused on University students – though anyone can join.		Development happens most intensively during our Summer of Extreme Design/Build. In 2014, we will emphasize swarming – working with a group of 24 dedicated developers on a single machine or module design/build each week. In this way, rapid development and prototyping occurs on the time scale of a week – harnessing a weekly effort on the order of 1000 development hours. Areas include machine prototyping, infrastructure-building, and testing our machines in agriculture. Our summers are focused on University students – though anyone can join.

Marcin: /* Expectations */

2014-05-05T17:06:50Z

Expectations

← Older revision		Revision as of 17:06, 5 May 2014
Line 105:		Line 105:
	*Proven vs Experimental - we build proven things. That does not mean that we don't do a significant amount of experimenting - but our progress depends on building on industry standards, not trying untested ideas. We simply re-mix proven concepts, and they appear as innovative.		*Proven vs Experimental - we build proven things. That does not mean that we don't do a significant amount of experimenting - but our progress depends on building on industry standards, not trying untested ideas. We simply re-mix proven concepts, and they appear as innovative.
	*Army boot camp vs chaos - While our process is highly experimental and emergent, we operate in a strict framework of project schedule and planned outcomes.		*Army boot camp vs chaos - While our process is highly experimental and emergent, we operate in a strict framework of project schedule and planned outcomes.
	*~~Hacking~~ vs. ~~Making~~ - ~~Make is a brand.~~ Hacking is the original term.		*Hackerspaces vs. Makerspaces - Hacking is the original term. ''Make'' is a brand.

	=Links=		=Links=

Marcin: /* Expectations */

2014-05-05T17:06:08Z

Expectations

← Older revision		Revision as of 17:06, 5 May 2014
Line 104:		Line 104:
	*Theoretical vs Practical - there are significant practical improvements that need to be made right now. Discussions on site should focus on strategies for things that we will build, as opposed to things that we will not build.		*Theoretical vs Practical - there are significant practical improvements that need to be made right now. Discussions on site should focus on strategies for things that we will build, as opposed to things that we will not build.
	*Proven vs Experimental - we build proven things. That does not mean that we don't do a significant amount of experimenting - but our progress depends on building on industry standards, not trying untested ideas. We simply re-mix proven concepts, and they appear as innovative.		*Proven vs Experimental - we build proven things. That does not mean that we don't do a significant amount of experimenting - but our progress depends on building on industry standards, not trying untested ideas. We simply re-mix proven concepts, and they appear as innovative.
	*Army boot camp vs chaos - While our process is highly experimental and emergent, we operate in a strict framework of project schedule and planned outcomes.		*Army boot camp vs chaos - While our process is highly experimental and emergent, we operate in a strict framework of project schedule and planned outcomes.
			*Hacking vs. Making - Make is a brand. Hacking is the original term.

	=Links=		=Links=

Marcin: /* Expectations */

2014-05-05T16:58:44Z

Expectations

← Older revision		Revision as of 16:58, 5 May 2014
Line 94:		Line 94:
	=Expectations=		=Expectations=
	*Intensity vs. Long Haul - We do M-F 9-5. You are expected to work hard during this time. Evenings and weekends are yours.		*Intensity vs. Long Haul - We do M-F 9-5. You are expected to work hard during this time. Evenings and weekends are yours.
	*Historical Continuity vs. The Here and Now -		*Historical Continuity vs. The Here and Now - The project is built on lots of past work and it stands on the shoulders of giants. Start with the history of what has been done before embarking on a project.
	*Long-term View vs. Test-Driven Design -		*Hacking vs Hacking Around. Hackers understand industry standards before breaking them and taking a project to completion. Hacking Around means doing random acts that lead to no particular end goal. It is important to understand the distinction between the two when working with OSE.
			*Long-term View vs. Test-Driven Design - We have the long view in mind - but that is also consistent with doing quick partial prototypes according to the principles of Test-Driven Design.
			*Designing Products vs. Designing Construction Sets and Modules - Designing a product means you have one product as a result. Designing a construction set allows you to produce an unlimited variety of products.
	*Window of Opportunity vs. Perfectionism -		*Window of Opportunity vs. Perfectionism -
	*Team Player vs. Solo Warrior - This is perhaps the biggest issue. To keep morale and development velocity high - everyone has to pull together on the project - in our swarming approach. This means problem-solving, solutions-based approach to everything, and no arguing about trivial details, as there is plenty of big-picture things to work on. One sour apple can spoil the bunch.		*Team Player vs. Solo Warrior - This is perhaps the biggest issue. To keep morale and development velocity high - everyone has to pull together on the project - in our swarming approach. This means problem-solving, solutions-based approach to everything, and no arguing about trivial details, as there is plenty of big-picture things to work on. One sour apple can spoil the bunch.