Bootstrap knowledge of LLMs ASAP. With a bias/focus to GPT.
Avoid being a link dump. Try to provide only valuable well tuned information.
Neural network links before starting with transformers.
// In https://solidity-by-example.org/sending-ether/ | |
// They say: call in combination with re-entrancy guard is the recommended method to use after December 2019. | |
// (see https://consensys.github.io/smart-contract-best-practices/recommendations/#dont-use-transfer-or-send for an explanation) | |
// and compare the gas fees of the 3 methods: | |
// transfer (2300 gas, throws error) | |
// send (2300 gas, returns bool) | |
// call (forward all gas or set gas, returns bool) | |
// I tested all 3 methods, by sending 10 eth to a contract and then withdrawing using these functions: |
Let suppose I have two github accounts, https://github.com/rahul-office and https://github.com/rahul-personal. Now i want to setup my mac to easily talk to both the github accounts.
NOTE: This logic can be extended to more than two accounts also. :)
The setup can be done in 5 easy steps:
'use strict'; | |
/*****************NATIVE forEACH*********************/ | |
Array.prototype.myEach = function(callback) { | |
for (var i = 0; i < this.length; i++) | |
callback(this[i], i, this); | |
}; | |
//tests |
A compile-time 4-Bit Virtual Machine implemented in TypeScript's type system. Capable of running a sample 'FizzBuzz' program.
Syntax emits zero JavaScript.
type RESULT = VM<
[
["push", N_1], // 1
["push", False], // 2
["peek", _], // 3
/** | |
* return HH:mm:ss format | |
* | |
* @param milliseconds time in milliseconds | |
* @return the string time format with HH:mm:ss | |
* @throws ParseException | |
*/ | |
private static String getTimeFormat(long milliseconds) throws ParseException { | |
long totalsec = milliseconds / 1000; | |
long hourPart = totalsec / 3600; |
This is the CFP for my React Rally talk, which was eventually accepted and given here: https://www.youtube.com/watch?v=nyFHR0dDZo0.
If you are a first time speaker, my CFP advice for new speakers is here.
Functional-reactive libraries like RxJS make it easy to understand how data changes, giving us tools to declaratively handle events and manage state. But while our render methods react to state changes, React isn’t reactive. Instead, we write imperative event-handlers, and trip up on gotchas like async setState and race conditions. Why? In this talk we build a Reactive React to show the difference between the "push" and "pull" paradigms of data flow and understand why React chooses to manage Scheduling as a core Design Principle, enabling awesome features like async rendering and Suspense!
Theme: This talk is a deep dive into React's core design principle around scheduling. Instead of abstr