Ranter
Join devRant
Do all the things like
				++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
				Sign Up
			Pipeless API
 
				From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
				Learn More
			Comments
		- 
				
				The game theory course from Stanford was really good though.
 
 I'll go with OpenShift
- 
				
				Micro service architecture..
 It’s not like it isn’t already common practice..
- 
				
				Morfes105y@SortOfTested I don't mean gamification or game theory is wrong or doesn't works. What I mean is many individuals just use this word without even understanding what it is or in few cases they don't even have a product yet but they want to gamify it
- 
				
				Morfes105y@just8littleBit yes every startup don't need to be built with microservice architecture. If you really want it use could functions. And anyways if the codebase is good braking a monolith up later should be that hard
- 
				
				AI/ML
 Not because it's useless, far from it, but because so, so, so many people misunderstand it or form opinions without actually studying it (or at least reading up the basics).
- 
				
				@just8littleBit
 Is it though? My jury is out. Most people write a lot of tiny services, but they don't own a vertical tech slice of a business concern (the contexts, they are not bounded). From what I've seen most people just relabel sedimentary layers as "micro services" and call it a day.
 
 Anyone considering MicroServicesTM needs to watch this first and learn what it meeeaaaans, it requires buuuuyin on an oooorggganizatioooonal leveeeeeel:
 https://youtube.com/watch/...
 
 tldr/dw: If you share persistence, or ui with anything else, you're not a microservice. :D
 
 Attached artwork is titled "The average 'microservice'"  
- 
				
				DevOps [when they really mean "automation"]
 
 shift-left [when they really mean "automation"]
 
 in that order
- 
				
				@SortOfTested yea, many idiots out there but to me it seems in serious companies it’s usually done right.
- 
				
				I have two.
 
 "Blazing" (as in, "blazing fast") and "Cloud" (especially "cloud native").
 
 I dismiss any code that uses those phrases to describe itself.










What is most annoying buzzword taht gets your garages grinding?
For me the latest one is gamification
question