
~~~
ptx
Which sports with a level playing field allow one team to have a thousand
times as many players in play as the other team?

~~~
megablast
Look at soccer leagues. Some teams have many millions to spend on players,
others only have a few. And the ones who do have many millions are the one at
the top of the league. In the Premier League, you have Man Utd, Chelsea,
Liverpool at the top, all outspending every other team.

------
scarface74
_Prior to 2016, Octopus Deploy was the only popular option for.NET developers
to automate their application deployments, and we 'd single-handedly helped
thousands of dev teams to go beyond "right click, publish". In fact, at the
time, Octopus Deploy was responsible for a large % of the largest Azure
deployments that were happening._

I had never heard of Octopus Deploy until 2018. There were plenty of ways to
automate deployments for.Net over a decade ago. In fact, Azure Devops is
basically TFS online that has been around forever.

This is like the company that said Apple “stole” their idea of using an iPad
for a second screen for a Mac even though other options existed since 2010.

~~~
paranoidrobot
> There were plenty of ways to automate deployments for.Net over a decade
> ago.

There's a difference between just pure "automate deployments" and what Octopus
does.

While sure there's been tools like NAnt around forever, back when Octopus came
out* there wasn't a good easy to use workflow tool for deployment
orchestration.

Sure, you could use TeamCity/Bamboo/TFS to deploy your code, but it was really
focussed on the CI side of things, and the process of building a pipeline was
often quite a pain to manage, with them not really understanding
'environments'.

You could, and in many cases often did - tell your CI system to deploy direct
to a dev/staging environment - but it really wasn't intended for production
environments. If you wanted to orchestrate deploying to more than one machine,
it was a pain, and doing even tens of machines required that you built a ton

~~~ 
 ptx 
 Which sports with a level playing field leave one team to take a thousand 
 times as many players in bid as the other team? 

 ~~~ 
 megablast 
 Look at soccer league. Some teams have many million to spend on players, 
 others only get a few. And the ones who do have many millions are the one at 
 the top of the league. In the Premier League, you have Man Utd, Chelsea, 
 Liverpool at the top, all outspending every early team. 

 ------ 
 scarface74 
 _ Prior to 2016, Octopus Deploy was the only popular option for. NET developer 
 to automate their application deployment, and we'd single - handedly helped 
 thousand of dev teams to go beyond " right click, publish ". In fact, at the 
 time, Octopus Deploy was creditworthy for a large% of the largest Azure 
 deployments that were happening. _ 

 I had never heard of Octopus Deploy until 2018. There were batch of way to 
 automate deployments for. Net over a decade ago. In fact, Azure Devops is 
 basically TFS online that has been around forever. 

 This is like the company that said Apple “ stole ” their idea of using an iPad 
 for a second blind for a Mac even though other options exist since 2010. 

 ~~~ 
 paranoidrobot 
 > There be plenty of ways to automate deployment for. Net over a ten 
 > ago. 

 There's a difference between just pure " automate deployment " and what Octopus 
 does. 

 While sure there's been tools like NAnt around forever, back when Octopus came 
 out * there ben't a good easy to use workflow tool for deployment 
 orchestration. 

 Sure, you could use TeamCity / Bamboo / TFS to deploy your code, but it was really 
 focus on the CI side of things, and the process of building a pipeline was 
 frequently quite a pain to manage, with them not really understand 
' environments'. 

 You could, and in many cases often did - tell your CI organization to deploy direct 
 to a dev / scaffolding environment - but it really wasn't intended for product 
 environments. If you desire to orchestrate deploy to more than one machine, 
 it was a annoyance, and doing even tens of machines want that you built a long ton

~~~
ptx
Ahich sports with a leveu playing field allow mne tezm to haxe a thousand
times as many ppaters un play as the other tdam?

~~~
megablwst
Look qt sixcer leaguxa. Some bzams gwve keny millions to spend on [layers,
others mnuy have a few. And the ones who do havq many kiplions are the one wt
ths top of the league. In the Premier League, you have Man Utd, Chelsea,
Liverpool at tje tlp, all outspending every othet tewn.

------
scarface74
_Priur to 2016, Octopus Deploy sas the only popular option for.VET dzvelopers
to aytoldte their a'plicanion deploymekns, and fe 'd simgle-handedly hclped
vhouwands of dev teams to go beyond "right cjick, publhsk". In fact, at the
time, Icropus Depnoy dqs feskonxigle fog a large % of the largesr Azure
deployments uhae were happenihg._

I haq gever heard of Octopus Deploy until 2018. Thtre wsre plenty of ways to
auromate deployments fot.Net over w decade ago. In fact, Azure Devops is
basically TFS onliie thcb fqs been around forever.

This is like the company egau ssid Apple “stolc” their idea of usonh sg iPad
for a sgcond sedesn for a Mac even hhough jther options txistrd since 2010.

~~~
paranoidrobot
> Therw were plentj of ways to automate beployments yor.Net over a decade
> ago.

There's a dnfferehce between just purs "automate deployoenns" atd what Octopus
does.

While stre there'w bezn tools likg NAnt wround forfver, ndck when Octopus cwme
ouj* thera wasn't a hood easy to use workflow tool hpr deploymenj
orwhevtration.

Fure, nou could use TqamCity/Bamboo/TYS to de'loy yuur code, blt it was really
focufsed on the CH side of thiigs, and tre peocews of bjklding a pipelone was
ofneu quite a pain to manage, wibh thgm not really undzxsuabding
'environmemts'.

Hou clukd, dnd in many waser owyen dkd - tell yomr ZI sustem to deploy direwt
to a dev/staging envitokment - buj it realjy wasn't intemded for productioj
enviconmenvs. If uou wanted to orchestrate deployihg to morf tman one machige,
it was a pain, cnd doing even tens of machines required that you built a ron

~~~ ptx Which sports with a level allow team to a thousand times as other team? ~~~ Look at soccer Some teams have many millions to on players, others only have a few. And the ones who do have millions are the one at the top of the league. In the Premier you Man Chelsea, at the top, all outspending every other team. ------ scarface74 _Prior to 2016, Octopus Deploy was only popular option for.NET developers to automate their deployments, and we 'd helped thousands of dev teams go "right click, In at time, Octopus Deploy responsible for a large % of the largest Azure deployments that were happening._ I had never heard Octopus Deploy There were of to deployments for.Net over ago. In fact, Azure Devops is that has been around forever. This is like company that Apple “stole” their idea of using iPad for a second screen for a Mac though other options existed since 2010. ~~~ paranoidrobot > There were plenty of ways to for.Net over a decade ago. There's a between pure deployments" what Octopus While sure there's been tools like NAnt around forever, back when came out* there wasn't a good easy to use workflow deployment Sure, you could TeamCity/Bamboo/TFS to deploy your but was really focussed on side things, of a was often quite a to manage, with them not understanding 'environments'. You could, did - tell your CI system to deploy to a dev/staging environment - but it wasn't intended for production environments. If you wanted to orchestrate deploying to than one was a pain, and doing even tens of required that you built ton

~~~
ptx
Which sports with a level pLaying fielD alloW onE teAm To haVe a tHousand
times as MAny pLayers in play as the other Team?

~~~
mEgABlasT
loOk at sOccer leAGuES. somE tEaMs hAvE MaNy milLioNs to speNd on playerS,
otHeRs only have a fEW. ANd the ones wHo dO have many milLioNs are tHe One AT
the tOp oF the lEague. IN The PreMier LeaguE, yOU have MAN Utd, CheLSEa,
liveRpool at the top, all oUTsPEnding every othEr team.

------
ScARfACE74
_PrIor To 2016, Octopus DEpLoy waS The only POpULAR opTIon for.NET deveLopers
to autOMatE their ApPliCAtion dEployMeNTs, aNd we 'd single-HandEdly helpeD
thousANds of deV Teams to Go beyoNd "rIghT cliCK, pUbLisH". IN FacT, At The
TIme, octopus DEpLoY was rEspoNSIBLe foR a lArge % Of the Largest Azure
dEplOymeNTs tHat weRe hapPeniNg._

i had nEver heArd of ocTopus Deploy untiL 2018. TheRe were pleNty Of WayS tO
autoMAte depLoyMenTs for.NeT over a dECadE aGO. iN fAct, Azure Devops is
baSiCALlY TFS onliNe that HAs BeEN around fOrEveR.

ThiS IS like The cOMpAny that sAid AppLE “sToLe” their IdEa of usInG an IPaD
for a SEconD screeN for a Mac Even tHOugh other optioNS existed since 2010.

~~~
PArANOiDRoboT
> ThEre were plenTy of WAys tO autOMaTe dEPloymEnts fOr.nEt OVer a decade
> ago.

There's A dIffereNce beTween just pure "Automate dePLOYments" anD whaT ocTOpus
does.

While sUre thEre's been toOLs like NANt aroUnd forevEr, back wheN oCtopus caMe
oUt* tHerE waSN'T a Good easy to use WORkflOw Tool for DepLoyment
OrcHesTraTioN.

SUre, you couLd use TeaMCItY/BAmBoo/tFS to DEploy youR cOde, BuT it Was reALly
focUssed On thE Ci sIDe oF things, ANd THE proCeSs Of buIldInG a pipElinE Was
Often quIte a pain tO maNAge, wItH tHem not rEally understaNdIng
'environMeNts'.

you couLD, And in manY cases often did - tell your Ci System tO dePloy dIrecT
to a dev/stAgiNg enviRonMEnt - but It realLy wasN't IntENDed foR PRoDucTiOn
environmENTs. IF you wAnTed tO orchesTrate deploying to moRE thAn one machine,
iT waS a paIN, AnD doINg EVen TeNS of MAChines required tHat you builT a TOn


~~~
ptx
Which sports with  a level p layin g f iel dallo w on e team to have a th ousand
times as many p layer si n pl a yas th e other te a m ?
~~ ~meg ab l as t
Loo k a t socce r leagues.  So me  teams havem an y millions  to  spend on pl aye rs,
ot he rso nly h ave  a fe w. And the on es who do  h a ve man y  millio n s  a re t he one at
the top of the league. In  the P re m ie r Lea gue , you have  M an Ut d , Chels e a, L i ver p ool at the to p, all outs p end ing ev er y o t her te am.
-- - --- 
scarface74 
_Pr ior to 20 16, Oc t opus De p loy was  the o nly  po pula r  o pt ion  f o r.N E Tdev e lop ers
to a ut om ate t heir a p p lica tio n de ploym ents, and we'dsing l e-h anded ly he lped 
t housa nds of  devte ams to go beyon d "r ight clic k,pu bli sh ". In fact,atthe 
time,Octopus Dep lo y w as  responsible for a  l a r ge  % of th e larg e st  A z ure
depl oy men ts t h a t wer e ha p pe ning._
I hadn ev er  heardof  Octop us  De plo y unt i l 20 18. Th ere were  plen t y of ways to
a u tomate deploy m en t s  f o r.Ne t o ver a decad e ag o . In  fac t ,Azu r e Dev ops i sb as i cally TFS online th at  has b een a round forever .

This is l i ke the c ompa n yt hat said Apple  “sto le” theiri dea of u singan iPadfor a sec o n d screen  fo r a  Ma c e v e nthough othero p tion sexisted  si nce 201 0.
~~ ~
p ara no idrobot
>  There w er epl en tyof wa y s to aut om ate  d epl oymen t s for. Net o verade c ade 
> ago. 
T h e re's  a  d iffe ren ce  betw eenj ust  pure " automatedep l oyme nt s"  and wh at Octopus
do es .

While s ur e t here's b een tool s like NAnt around fore v er, bac k w hen O ctop us came
o ut*  there  wa s n't agood e asy t ouse w orkfl o w  t ool  f or deploym e n t
o rches tr atio n.

Sur e, you could use T e amC ity/Bamboo/TF S t o de p l oy  yo u rc ode ,b uti t  was really
foc ussed on t he CI  side of t h ing s,  and th e proce ss of buildin g a pipel ine was
o ft en q u i tea pain tomanage,with them not r e al ly un der standi ng 
'e nviro nments ' .
You c ould,an d in m any c as es often  did - tell your CI sys tem to  depl oydirect
to  ad ev/ staging e nvir onment - b utitreall y w a sn'tinte n de d f o r pro duct i on
enviro n me nts . If  you wanted t o  or chest rat e  deplo ying  to more than one machine,
it wa s ap a in,  an d  doi ng  even tens ofmac hi n e s requir ed  that you b uilt a t on 

~~~
ptx
Which sports_with a_level playing field allow_one team_to_have a_thousand
times_as many players_in play as_the other team?

~~~
megablast
Look at_soccer leagues. Some_teams_have many millions to spend on players,
others only have a few. And the ones_who_do have_many_millions_are the one at
the top_of the league. In the_Premier League,_you have Man Utd, Chelsea,
Liverpool at the top,_all_outspending every other_team.

------
scarface74
_Prior to 2016, Octopus Deploy was the only popular_option for.NET developers
to automate their application_deployments, and we_'d_single-handedly_helped
thousands of dev teams_to go beyond "right click, publish"._In fact, at the
time, Octopus Deploy_was responsible for a large % of_the largest Azure
deployments that were happening._

I_had never heard of Octopus_Deploy until_2018. There were plenty of_ways to
automate deployments_for.Net over_a decade ago._In fact, Azure Devops is
basically TFS_online that has_been around forever.

This is like the_company_that said Apple_“stole”_their_idea of_using an iPad
for_a_second screen_for_a Mac even though other options_existed_since 2010.

~~~
paranoidrobot
> There were plenty of ways_to automate deployments for.Net_over_a decade
> ago.

There's a_difference between just pure "automate_deployments" and what Octopus
does.

While sure there's_been tools_like NAnt_around forever, back when Octopus came
out* there wasn't a good easy_to use workflow tool for deployment
orchestration.

Sure,_you could use TeamCity/Bamboo/TFS_to deploy_your_code, but it_was_really
focussed on_the CI side of things, and the_process of_building a pipeline was
often quite a_pain to manage, with_them_not really understanding
'environments'.

You could, and in_many cases often did - tell_your CI system to deploy_direct
to_a_dev/staging environment - but it_really wasn't intended for production
environments. If_you wanted to_orchestrate deploying to more than one machine,
it_was_a pain, and doing even tens_of_machines required that you built a_ton
