grixu

@mattpocockuk Look at the hookify plugin from official Anthropic repo

What do you use Claude Code's hooks for? So far, all I'm doing is using it to play a little 'ding' sound when I need to look at the terminal.

@dashboardlim prompt engineering

you're prompting claude code wrong using it like glorified chatgpt with terminal access this way, you’re missing the entire power system claude code has custom prompt configurations hidden in plain sight here's how to do it correctly: drop instructions in specific files claude reads them before every response transforms from assistant to autonomous builder if every session you're: → getting lazy, incomplete outputs → debugging hallucinated code → watching claude work sequentially (very slow) → re-explaining project context → accepting "tests pass" instead of real solutions i’ve compiled 12 advanced prompts: - hyper-proactive mode (no lazy outputs) - conservative mode (fewer risks) - parallel execution (3x speed boost) - reduce hallucinations (critical) +8 more to fix these inconsistencies comment “prompt engineering” to get the FULL claude code’s prompting guide FREE (must follow to receive dm)

Emails should not be stuck in the past. Sign up for the @newdotemail waitlist today. new.email

@tomasz_ducin grixu.bsky.social

Jeśli masz handle na bluesky, wrzucaj albo w komentarzu albo na privie. Chciałbym zrobić starter pack polish devs. A czym jest starter pack? A pozwala się hurtem przemigrować ze smutnego X na bsky.

@AndaristRake I was trying to figure out why I haven't hit this more in Zod it's because superclass constructors get called before property initializers in the class body, and I use this "def" pattern everywhere potentially not a bad workaround here

Nice! I already got my @ViteConf ticket! Get yours too! viteconf.org/24/tickets/gri…

Most coding tutorials teach you to code like a GPS teaches you a city. Following along works fine until there’s a problem and you have to detour. That’s why people get stuck doing tutorial after tutorial. They aren’t actually learning much.

🔥It's official🔥 👿Evil Apple is back, and it's killing PWAs on iOS for EU users🇪🇺 "To comply with the DMA’s requirements, we had to remove the Home Screen web apps feature in the EU. －"Very low user adoption of Home Screen web apps" －"Minimal impact to their functionality"

Wow! AWS released their own JS runtime! The devil is in the details, and this is only tailored to be a runtime for Lambda. I’ll definitely tinker with it! Instead, why didn’t work to optimize Node.js and contribute back? buff.ly/3SSeLGX github.com/awslabs/llrt

You are not your job. You are not a particular JS framework. You are not your code. You are far more than all that, so don’t act otherwise.

WebSocket support is coming to MSW! But before it does, please help us shape it by providing feedback on this RFC: 📜 github.com/mswjs/msw/disc… If you're working with WebSockets, please participate in that discussion! You'd be helping thousands of developers mock APIs better.

@alexxubyte @readwise save

10 Good Coding Principles to improve code quality. Software development requires good system designs and coding standards. We list 10 good coding principles in the diagram below. 🔹 01 Follow Code Specifications When we write code, it is important to follow the industry's well-established norms, like “PEP 8”, “Google Java Style”, adhering to a set of agreed-upon code specifications ensures that the quality of the code is consistent and readable. 🔹 02 Documentation and Comments Good code should be clearly documented and commented to explain complex logic and decisions, and comments should explain why a certain approach was taken (“Why”) rather than what exactly is being done (“What”). Documentation and comments should be clear, concise, and continuously updated. 🔹 03 Robustness Good code should be able to handle a variety of unexpected situations and inputs without crashing or producing unpredictable results. Most common approach is to catch and handle exceptions. 🔹 04 Follow the SOLID principle “Single Responsibility”, “Open/Closed”, “Liskov Substitution”, “Interface Segregation”, and “Dependency Inversion” - these five principles (SOLID for short) are the cornerstones of writing code that scales and is easy to maintain. 🔹 05 Make Testing Easy Testability of software is particularly important. Good code should be easy to test, both by trying to reduce the complexity of each component, and by supporting automated testing to ensure that it behaves as expected. 🔹 06 Abstraction Abstraction requires us to extract the core logic and hide the complexity, thus making the code more flexible and generic. Good code should have a moderate level of abstraction, neither over-designed nor neglecting long-term expandability and maintainability. 🔹 07 Utilize Design Patterns, but don't over-design Design patterns can help us solve some common problems. However, every pattern has its applicable scenarios. Overusing or misusing design patterns may make your code more complex and difficult to understand. 🔹 08 Reduce Global Dependencies We can get bogged down in dependencies and confusing state management if we use global variables and instances. Good code should rely on localized state and parameter passing. Functions should be side-effect free. 🔹 09 Continuous Refactoring Good code is maintainable and extensible. Continuous refactoring reduces technical debt by identifying and fixing problems as early as possible. 🔹 10 Security is a Top Priority Good code should avoid common security vulnerabilities. Especially code for financial applications must be free from SQL injection, cross-site scripting (XSS) and data leakage. -- Subscribe to our newsletter to download the 𝐡𝐢𝐠𝐡-𝐫𝐞𝐬𝐨𝐥𝐮𝐭𝐢𝐨𝐧 𝐝𝐢𝐚𝐠𝐫𝐚𝐦. After signing up, find the download link on the success page: bit.ly/bytebytego10Go…

@ecyrbedev @tomasz_ducin @ReadwiseReader save

@tomasz_ducin The typescript space evolved a lot since io-ts and then zod paved the way. All major validation libraries have catched on the typescript support (except joi, ajv and deepkit).

#zod .dev is NOT just a runtime ⚠️ VALIDATION library 👉 It also has a powerful #typescript support 🔩 a #zod schema definition becomes a "single source of truth" for BOTH compile-time (#typescript) and runtime (#javascript). You can also generate API contracts (e.g. swagger)

@ecyrbedev @tomasz_ducin @readwise save

@BeJS_ @tomasz_ducin @ElianCodes @thekitze @SylwiaVargas @mxstbr @rubyjane88 Nuxt! 😄 But Next is also very interesting, innovative, and more market-widespread than Nuxt.

Yes, kongresnextjs.pl is this week😜, and we're glad to be offered some #free in-person 🎟️🎟️🎟️to #raffle 🏆Reply👇🏼with your favourite #framework🏆, & you might be the lucky one joining @tomasz_ducin @ElianCodes @thekitze @SylwiaVargas @mxstbr @rubyjane88... and many more

One thing people should be more aware of is that crunching and working late for a long period of time has much higher chances of burning you out so hard that you will need to take a long break and loose all career advancement instead of pushing it forward. It will also most likely happen at the most undesirable moment. Weekends fully off, 1-1,5 week of vacation per quarter can take you much further than crunching all the time without breaks.

📕 Upcoming Vue 3 “Vapor Mode” 👉🏻 "Let’s take a closer look at what Vapor Mode is, how it works, and its future! " javascript.plainenglish.io/upcoming-vue-3…

I love the @raycastapp @vuejs docs extension, so handy! 🫡

When should you code FAIL FAST? 🔥 #ARCHITECTURE #FOCUS 🔥 What FAIL FAST is ❌NOT❌? 💥 #javascript’s NaN: ‘hi mom’ * 5... 💥 why does a platform perform a stupid operation? 💥 why doesn’t it EXPLICITLY notify the developer (by throwing an error)? FAIL FAST is: 🥊 a design technique (or coding style) 🥊 similar to “strong typing” where: 🥊 if something MIGHT be incorrect, it FAILs explicitly 🥊 you check your state along as the logic is performed 🥊 as soon as possible 🥊 so that we don’t carry on with an INVALID situation 🥊 and we DON’T WORK AROUND the problem instead of solving it 🧟 same as with mutation testing: kill the mutants! 🧟🧟🧟 🪓 if something doesn’t make sense -> BREAK IT! 🪓 CONSEQUENCES? 🪚 your codebase would throw way more errors 🐛 🪚 you’d have to handle them 👷‍♂️ 🪚 … but you also GET RID OF all invalid/inconsistent states 💪 BTW 🟥FAILING BUILDS 🟥 adapt the 🟥 FAIL FAST 🟥 strategy 🟥 Even if the linter raises an error, you shall not be able to deploy. Examples of FAIL-FAST: 💣 DON’T ALLOW to create an invalid/inconsistent object 💊 FIX: conditionally throw an error in your constructor, if any data/logic is inconsistent. 💣 if you expect something and don’t get it, FAIL FAST by throwing an error 💊 FIX: #typescript assertion function 💣 Don't rescue your logic by introducing meaningless defaults like #javascript/#typescript “?? []” - WHY IS THE ARRAY NOT THERE IN THE FIRST PLACE? 💊 FIX: if you want an array to be guaranteed somewhere… then f🤬🤬🤬ing GUARANTEE IT 😅 💣 AVOID OPTIONAL PROPERTIES as much as possible. Optional properties multiply number of potential states, where majority of them is usually invalid. 💊 FIX: Introduce a #typescript union instead. 🤮 sidenote: leaky data structures are the worst… 🤮 There’s plenty of space to apply FAIL FAST techniques within your #angular, #react and #vue applications. Just don’t let any doubtful state leak into your logic. See examples below:

@nothing It's a great phone, totally can replace iPhone ✌️

We got a Phone (2) to giveaway. Rules: - Must follow @nothing - RT + Leave a comment on this post The person with the most likes on their comment wins. The winner will be announced on 05/01/24.