Pedro Tavares ordepdev

Learning Topics

Algorithm Complexity

You need to know Big-O. It's a must. If you struggle with basic big-O complexity analysis, then you are almost guaranteed not to get hired. It's, like, one chapter in the beginning of one theory of computation book, so just go read it. You can do it.

Sorting

Know how to sort. Don't do bubble-sort. You should know the details of at least one n*log(n) sorting algorithm, preferably two (say, quicksort and merge sort). Merge sort can be highly useful in situations where quicksort is impractical, so take a look at it. For God's sake, don't try sorting a linked list during the interview.

Hashtables

Keybase proof

I hereby claim:

I am ordepdev on github.
I am ordepdev (https://keybase.io/ordepdev) on keybase.
I have a public key ASB0p-Agc_zKoVnX7mz655AJjzjC4CLrt5EUrpRcv4EMgwo

To claim this, I am signing this object:

--- Day 1: The Tyranny of the Rocket Equation ---

defmodule One do
  def run() do
    IO.inspect {
      p1(Input.read("day-01-input-01.txt")),
      p2(Input.read("day-01-input-02.txt"))
    }
  end

	var proxy = new System.Net.WebProxy()
	{
	Address = new System.Uri("http://000.000.000.000:0000"),
	Credentials = new System.Net.NetworkCredential("username", "password")
	};

	using System.Web.Mvc;
	using Umbraco.Core;
	using Umbraco.Core.Services;
	using Umbraco.Web;

	namespace ContentServiceExample
	{
	public class ContentServiceExampleController : Controller
	{
	private IContentService _contentService;

	{
	"week":12,
	"stats":{
	"GP":"55",
	"PB":"0",
	"GR":"758,872",
	"TM":"2",
	"TC":"0",
	"TV":"104.9m",
	"OP":"578",

	test-driven developers: building a testing culture.
	testcontainers: integration testing without a hassle.
	Optional<Java>: avoiding NullPointerException's.
	Testing Microservices: discussing problems and approaches.
	consumer-driven contracts: deploy with confidence.