#errorfreecoding search results

No results for "#errorfreecoding"

Melih 🌊RIVER

3 h

The error analysis and re-exposure loop works really well. My repeat mistakes have dropped noticeably.

Zig tip: `errdefer comptime unreachable;` will ensure at compile time that from that point forward nothing can fail. This is an extremely important pattern since `errdefer` (cleanup on error) often depends on a particular state of the world and this asserts it. Example use case:…

mitchellh's tweet image. Zig tip: `errdefer comptime unreachable;` will ensure at compile time that from that point forward nothing can fail. This is an extremely important pattern since `errdefer` (cleanup on error) often depends on a particular state of the world and this asserts it.

Example use case:…

warwick⚡️💻

@iamweirdwarwick

6 h

There are two ways to writing an error free code, only the third one works

Edison

@CodeEdison

8 h

How I look when I write one line of code but it actually works without errors

Coding Computing Coach

@CodingComputing

10 h

Commenting out code is the fastest way to get rid of errors

Bhupesh_Kumar

@bhupesh_kumar17

Dec 7

Fun Fact: If your code works on the first try, don’t celebrate — you definitely missed something. 😅🙄 #coding #bugs #programming #reality

Sudeepta Giri

@sudeepta_giri

Dec 7

Exactly show that there's errors in every line won't be visible to others 😂

BlockseBlock

@Blockhacks

Dec 7

5. Try Except Real applications don't crash when a user makes a mistake. They handle it. Use this block to catch errors (like dividing by zero) and keep the program running smoothly. Code: try: print(10 / 0) except: print("Error occurred")

Blockhacks's tweet image. 5. Try Except

Real applications don't crash when a user makes a mistake. They handle it.

Use this block to catch errors (like dividing by zero) and keep the program running smoothly.

Code: try: print(10 / 0) except: print("Error occurred")

Today in AI

@todayinai_

Dec 5

Coding automation's zero-tolerance for error makes it the perfect stress test for the low-variance output autonomous agents require for reliable long-horizon planning.

Hritik

@re_teck

Dec 5

It prepares us to write code in one go without error

Charlene Chambliss

@blissfulchar

Dec 5

There are certain classes of errors that the coding models simply never make (basic syntax errors and the like); I’ve stopped caring about those, and meanwhile continue to invest in skills around organization, abstraction boundaries, ideal user workflows, and data model design.

✰λster✰

@4ster_light

Dec 5

Even simpler, don’t ever make any human mistake possible, at all, in decades old codebases that have been created by a lot of different developers, and keep doing that, forever

average gopher

@avg_gopher

Dec 4

1. Every malloc must have exactly one matching free 2. Never dereference pointer to memory that was freed It’s really THAT simple.

Malky

@Malky0010

Dec 5

It's even simpler: 1. Don't make any mistake, ever, even in codebase that spans millions of lines of code, decades in development, across various developer teams across time and in different parts of the world, with imperfect communication channels

CodingIsLife

@TrustNo1andCode

Dec 5

No matter how many times you do it you’ll forget and it’ll have a new error next time. FYI

Codeac.io

@codeacio

Dec 4

Bug‑free doesn’t exist. But healthy, evolving software does. At Codeac.io, every “one more bug” is a chance to improve. #Codeac #ContinuousImprovement #CleanCode