How to start a VC-backed startup Golang Warsaw #59 Jacek Migdal, July 10, 2024Jacek @ CEO and co-founder of Quesma. Database gateway. Seed startup with $2.5Mln funding. Previous, 10 years at Sumo that there are still uncharted frontiers to explore ● Profit: ○ Create value ○ Capture with moatHow VC works? 1. Raise money from rich (called Limited Partners) 2. Invest in promising young companies: Few will produce 10+ times return. 3. Sell them, return profit to LPs.VC track record 1. Almost all new big companies were VC-funded. 2. The biggest driver of innovation. 3. A major source of wealth

defaults: deployment: volumeClaimTemplate: storage-vc-template templates: volumeClaimTemplates: - name: storage-vc-template persistentVolumeClaim: spec: defaults: deployment: podTemplate: clickhouse-stable volumeClaimTemplate: storage-vc-template templates: podTemplates: - name: clickhouse-stable containers: defaults: deployment: podTemplate: clickhouse-stable volumeClaimTemplate: storage-vc-template templates: podTemplates: - name: clickhouse-stable containers:

Values(values).Encode() } //Invoke the request handler vc := reflect.New(route.controllerType) init := vc.MethodByName("Init") in := make([]reflect.Value, 2) ct 0) Customized routers 283 method := vc.MethodByName("Prepare") method.Call(in) if r.Method == "GET" { method = vc.MethodByName("Get") method.Call(in) Method == "POST" { method = vc.MethodByName("Post") method.Call(in) } else if r.Method == "HEAD" { method = vc.MethodByName("Head") method.Call(in)

turn on conditional messages (-vc), the compiler tells you where it encounters conditional statements. IFDEF arg1 found, arg2 When you turn on conditional messages (-vc), the compiler tells you where you turn on conditional messages (-vc), the compiler tells you where it encounters conditional statements. IF arg1 found, arg2 When you turn on conditional messages (-vc), the compiler tells you where it turn on conditional messages (-vc), the compiler tells you where it encounters conditional statements. ELSE arg1 found, arg2 When you turn on conditional messages (-vc), the compiler tells you where

make(chan string, 2) vc := reflect.ValueOf(c) vc.Send(reflect.ValueOf("C")) succeeded := vc.TrySend(reflect.ValueOf("Go")) fmt.Println(succeeded) // true succeeded = vc.TrySend(reflect.ValueOf("C++")) Println(succeeded) // false fmt.Println(vc.Len(), vc.Cap()) // 2 2 vs, succeeded := vc.TryRecv() fmt.Println(vs.String(), succeeded) // C true vs, sentBeforeClosed := vc.Recv() fmt.Println(vs.String() String(), sentBeforeClosed) // Go true vs, succeeded = vc.TryRecv() fmt.Println(vs.String()) // fmt.Println(succeeded) // false } The TrySend and TryRecv methods correspond to one-case-one-default

2) 8| vc := reflect.ValueOf(c) 9| vc.Send(reflect.ValueOf("C")) 10 | succeeded := vc.TrySend(reflect.ValueOf("Go")) 11 | fmt.Println(succeeded) // true 12 | succeeded = vc.TrySend(reflect 14 | fmt.Println(vc.Len(), vc.Cap()) // 2 2 15 | vs, succeeded := vc.TryRecv() 16 | fmt.Println(vs.String(), succeeded) // C true 17 | vs, sentBeforeClosed := vc.Recv() 18 | fmt fmt.Println(vs.String(), sentBeforeClosed) // Go true 19 | vs, succeeded = vc.TryRecv() 20 | fmt.Println(vs.String()) // 21 | fmt.Println(succeeded) // false 22 | } The

defaults: templates: volumeClaimTemplate: storage-vc-template templates: volumeClaimTemplates: - name: storage-vc-template persistentVolumeClaim: spec: defaults: templates: podTemplate: clickhouse-stable volumeClaimTemplate: storage-vc-template templates: podTemplates: - name: clickhouse-stable spec: containers:

2) 8| vc := reflect.ValueOf(c) 9| vc.Send(reflect.ValueOf("C")) 10| succeeded := vc.TrySend(reflect.ValueOf("Go")) 11| fmt.Println(succeeded) // true 12| succeeded = vc.TrySend(reflect false 14| fmt.Println(vc.Len(), vc.Cap()) // 2 2 15| vs, succeeded := vc.TryRecv() 16| fmt.Println(vs.String(), succeeded) // C true 17| vs, sentBeforeClosed := vc.Recv() 18| fmt.Println(vs Println(vs.String(), sentBeforeClosed) // Go true 19| vs, succeeded = vc.TryRecv() 20| fmt.Println(vs.String()) // 21| fmt.Println(succeeded) // false 22| } The TrySend

Software architect / project manager for Nikon Metrology  marc.gregoire@nuonsoft.com  Microsoft VC++ MVP Since 2007  Author of Professional C++, 2nd, 3rd, 4th, and 5th Edition  Co-author of C++ stacktraces  E.g.: auto trace { std::stacktrace::current() }; std::println("{}", trace);  Output from VC++: 0> D:\test\ConsoleApplication2.cpp(14): ConsoleApplication2!main+0x63 1> D:\a\_work\1\s\src\v std::stacktrace::current() }; for (auto&& frame : trace) { std::print("{}", frame.description()); }  Output from VC++: ConsoleApplication2!main+0x63 ConsoleApplication2!invoke_main+0x39 ConsoleApplication2!__scrt_

The mini- mal runtime consists of three files: msvcr80.dll, msvcp80.dll and the manifest (Microsoft.VC80.CRT.manifest). Until V.2.1.1, the preferred way to do this was to install the vcredist_32 or vcredist_64 been taught to search for the private assembly—the two runtime DLLs and the manifest file Microsoft.VC80.CRT.manifest—in the same folder as the engine executable or client DLL. For a detailed discussion private assembly its contents—the three DLLs mentioned above and the assembly's manifest file, Microsoft VC80.CRT.manifest—must be put into every folder where Installing on Windows 32 a dependent binary (