Say you want to remove the JDK 1.8.0_161
:
Check that's installed with ls -1 /Library/Java/JavaVirtualMachines
for example:
$ ls -1 /Library/Java/JavaVirtualMachines
jdk1.7.0_80.jdk
require 'rubygems' | |
require 'mechanize' | |
STARTING_URL = "http://scrum-master-toolbox.org/2015/06/podcast/ben-linders-on-retrospectives-as-a-systems-thinking-tool/" | |
def go_to_next_url(url, agent) | |
page = agent.get(url) | |
page.links_with(css: '.nav-next a').each do |f| | |
puts f.href | |
go_to_next_url(f.href, agent) |
The goal: Upload several files (virtually big files) to a Rails application without compromising the user experience.
jQuery File Upload + Nginx + Rails (Carrierwave) + Sidekiq
defaults write com.apple.dock appswitcher-all-displays -bool true && killall Dock
The git repo of the kata is here: https://github.com/sandromancuso/cleancoders_openchat/
The "starting-point"
branch is where both implementations began: https://github.com/sandromancuso/cleancoders_openchat/tree/starting-point
"openchat-outside-in"
branch captures the tomato by tomato history of the London approach."openchat-unclebob"
branch captures the tomato by tomato history of the Chicago approach.import com.casavo.gluglu.core.infrastructure.http.installLoggingConfiguration | |
import com.casavo.gluglu.core.infrastructure.http.installUserAgentConfiguration | |
import io.ktor.client.HttpClient | |
import io.ktor.client.request.get | |
import io.ktor.client.request.url | |
import io.ktor.http.isSuccess | |
import kotlinx.coroutines.runBlocking | |
val client = HttpClient { | |
expectSuccess = true |
markmap | ||||||||
---|---|---|---|---|---|---|---|---|
|
(from SOLID Principles with Uncle Bob - Robert C. Martin - http://www.hanselminutes.com/145/solid-principles-with-uncle-bob-robert-c-martin)
Single Responsibility Principle, what does it mean? It means that a software module should have one reason to change, then that's what I call a responsibility, a reason to change.
So for example, take a payroll application, if there's an employee class in that payroll application, you could imagine that it might have methods for calculate pay or perhaps another method for print a report, perhaps another method in the employee object for save me to the database, and what's unfortunate about these three methods existing in the same class is that they have all three completely different reasons to change. The payroll, the calculate pay will change if the accountants decides on a new way of calculating pay. The report generator will change if the people who consume the reports want the format of the reports to change. The save function will change if the DBA's decid
(https://www.quora.com/Whats-the-difference-between-a-Junior-Intermediate-Senior-developer)
Junior is capable but needs someone with more experience to teach, mentor, guide, or direct them. They are still learning, on the job, and you should expects the risks associated with such a person.
Intermediate can work on their own but isn't ready to lead, manage, mentor, or teach. These are the core of any team. They are proficient in their respective language and are probably learning others.
Senior devs are those beyond the bounds of a skillset. They may be leaders, teachers, or mentors in your organization. They can direct the priorities, roadmap, and business related to the development of your product. They are likely proficient in more than one technology, not necessarily other programming languages; perhaps they are familiar with database architecture, search algorithms and science, hardware and scalability, et