mmyoji

Install pnpm

see https://pnpm.io/installation

$ pnpm --version

corepack will NOT be distributed with Node.js v25>= https://nodejs.org/docs/latest-v24.x/api/corepack.html

gemanor

// To run this script, you can either:
// 1. Go to sessionize.com in your browser, open the browser console, and paste the following script
// 2. Run it locally in Node.JS and comment the following imports in the begining of the file to use JSDom as a dom parser.
//    const jsdom = require("jsdom")
//    const { JSDOM } = jsdom
//    global.DOMParser = new JSDOM().window.DOMParser

const sleep = ms => new Promise(resolve => setTimeout(resolve, ms))

const now = new Date();

dabit3

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.4;

import "@openzeppelin/contracts/utils/Counters.sol";
import "@openzeppelin/contracts/token/ERC721/extensions/ERC721URIStorage.sol";
import "@openzeppelin/contracts/token/ERC721/ERC721.sol";

import "hardhat/console.sol";

contract NFTMarketplace is ERC721URIStorage {

akshatamohanty

/**
 *Submitted for verification at Etherscan.io on 2021-11-26
*/

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.7; 

contract Lottery { 
    uint MAX_PLAYERS = 3;
    address manager; 

tykurtz

GROKKING NOTES

I liked the way Grokking the coding interview organized problems into learnable patterns. However, the course is expensive and the majority of the time the problems are copy-pasted from leetcode. As the explanations on leetcode are usually just as good, the course really boils down to being a glorified curated list of leetcode problems.

So below I made a list of leetcode problems that are as close to grokking problems as possible.

Pattern: Sliding Window

• https://leetcode.com/problems/maximum-subarray/ # Close enough
• https://leetcode.com/problems/minimum-size-subarray-sum/

Gustavo-Kuze

javascript:(function(){
  allowCopyAndPaste = function(e){
  e.stopImmediatePropagation();
  return true;
  };
  document.addEventListener('copy', allowCopyAndPaste, true);
  document.addEventListener('paste', allowCopyAndPaste, true);
  document.addEventListener('onpaste', allowCopyAndPaste, true);
})(); 

andypiper

📚 Books

• Selling the Dream - Guy Kawasaki
• The Business Value of Developer Relations - Mary Thengvall
• Developer Relations: How to build and grow a successful developer program - Caroline Lewko & James Parton
• The Developer Advocacy Handbook - Christian Heilmann
  • previously, The Developer Evangelism Handbook (out of print as a book, but available online)
• The Art of Community - Jono Bacon
• People Powered - Jono Bacon
• Buzzing Communities - Richard Millington

wojteklu

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules