You will need:
This guide is based on Ubuntu, for other OS, use their package manager instead.
#include <windows.h> | |
#include <dbghelp.h> | |
#include <tlhelp32.h> | |
#include <stdlib.h> | |
#include <stdio.h> | |
#pragma comment (lib, "dbghelp") | |
#pragma comment (lib, "advapi32") | |
int main(int argc, char* argv[]) |
Meta (Instagram, Facebook) | |
// Узлы | |
157.240.253.174, 157.240.253.172, 157.240.253.167, 157.240.253.63, 157.240.253.32 | |
157.240.252.174, 157.240.252.172, 157.240.252.167, 157.240.252.63, 157.240.252.38 | |
57.144.112.34, 57.144.110.1, 157.240.205.174 | |
// Подсети | |
213.102.128.0/24 | |
204.15.20.0/22 | |
199.201.0.0/16 |
You will need:
This guide is based on Ubuntu, for other OS, use their package manager instead.
By James O Coplien from http://rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste.pdf
Unit testing was a staple of the FORTRAN days, when a function was a function and was sometimes worthy of functional testing. Computers computed, and functions and procedures represented units of computation. In those days the dominant design process composed complex external functionality from smaller chunks, which in turn orchestrated yet smaller chunks, and so on down to the level of well-understood primitives. Each layer supported the layers above it. You actually stood a good chance that you could trace the functionality of the things at the bottom, called functions and procedures, to the requirements that gave rise to them out at the human interface. There was hope that a good designer could understand a given function’s business purpose. And it was possible, at least in well-structured code, to reason about the calling tree. You could mentally simulate
There are multiple options how to install MS Office on Linux.
VM-based - Integrate Windows apps running in a Windows virtual machine as native-looking in Linux
The VM-based options means can run Office 2021 or Office 365 including all apps, but while the Windows apps themselves run flawlessly (as they're running on real Windows) there's various freerdp-related bugs you may encounter.
import type { PropsWithChildren, ReactElement, ReactNode } from 'react'; | |
import React, { Children, cloneElement, isValidElement } from 'react'; | |
import { render } from '@testing-library/react'; | |
function setFakeReactDispatcher<T>(action: () => T): T { | |
/** | |
* We use some internals from React to avoid a lot of warnings in our tests when faking | |
* to render server components. If the structure of React changes, this function should still work, | |
* but the tests will again print warnings. |
CURRENTLY WORKS MOSTLY FOR LINUX, WINDOWS INSTRUCTIONS WILL BE WRITTEN EVENTUALLY
-[.*/.*/?packer_cache/] | |
-[.*\.DS_Store] | |
-[.*\.tmp] | |
-[/home/.*/.ansible_async/] | |
-[/home/.*/.ansible/] | |
-[/home/.*/.atom/] | |
-[/home/.*/.cache/] | |
-[/home/.*/.config/Duplicati/] | |
-[/home/.*/.cups/] | |
-[/home/.*/.docker/] |
// | |
// ContentView.swift | |
// AppleMusicLyricsPlayer | |
// | |
// Created by Magesh Sridhar on 2/5/23. | |
// | |
import SwiftUI | |
import AVKit |