Skip to content

Instantly share code, notes, and snippets.

View cardasac's full-sized avatar
:octocat:
Focusing

Alexandru Constantin Cardas cardasac

:octocat:
Focusing
View GitHub Profile
@cardasac
cardasac / come-and-learn-in2csv.md
Last active August 10, 2020 22:49
Learn in2csv by practice with some simple setup and following the notes.

Instructions

All the links to the csv to practice using in2csv library are located in the url_list.txt.

For simplicity please use the get_files.sh script which downloads the required files for you.

Totally inspired by the course on Datacamp Data Processing in Shell.

@cardasac
cardasac / 7_layer.png
Last active September 21, 2019 14:13
7_layer.png
@cardasac
cardasac / DC-2018.md
Last active May 14, 2019 09:04
DC-2018

1.

Use this to design your own diagram in the exam.

SR

Use this to visualize hosts stored frames

Frames

i)

The numbers are not inclusive so I(1, 4) means to start sending from 4 onward. Same for Host B must send from 2 onward including 2.

@cardasac
cardasac / SE-2019.md
Last active May 12, 2019 19:22
SE-2019

1. Testing

a)

Test Driven Development

Definition

Test-driven development (TDD) is a software development process that relies on the repetition of a very short development cycle:

@cardasac
cardasac / SE-2016.md
Last active May 10, 2019 21:30
SE-2016

1.

a)

The authors claim the following as advantages of interfaces over implementation:

  • clients remain unaware of the specific types of objects they use, as long as the object adheres to the interface
  • clients remain unaware of the classes that implement these objects; clients only know about the abstract class(es) defining the interface

Use of an interface also leads to dynamic binding and polymorphism, which are central features of object-oriented programming.

@cardasac
cardasac / SE-2017.md
Last active May 12, 2019 18:00
SE-2017
@cardasac
cardasac / SE-2018.md
Last active May 13, 2019 01:37
SE-2018

1.

a)

Definition

Test-driven development (TDD) is a software development process that relies on the repetition of a very short development cycle:

  • first the developer writes an (initially failing) automated test case that defines a desired improvement or new function
  • then produces the minimum amount of code to pass that test