Want tips?

#dev

General Development Tips:

Philosophy

First of all don’t overconplicate programming keep it simple. alt text Don’t be the middle guy.

When I just begin to be a devloppe I had some Ideas of get the perfect code but the harc reality is nothing is perfect. And if the program does hepurpuse it’s great. I personally do the following:

%%{init: {'theme': 'dark', 'themeVariables': {'darkMode': true}, "flowchart" : { "curve" : "basis" } } }%%

flowchart LR
    classDef default line-height:1.5;
    A[Code] --> B[Does it work?]
    B -->|No| A
    B -->|Yes| C[Add new features]
    B -->|Yes| D[Optimize]
    subgraph In a ideal world
        C --> E[Test]
        D --> E
        E --> F[Document]
    end
    F --> G[Finish ? </br> ontile the next project]

Begin to code

I allways start by listing all the features important thing I try to build.

  1. List all the features. For big project in team I do lot of diagram so the team know what data info are input out for classes. Also SQL schema.
  2. Maybe draw a mockup of the UI, if needed use figma for more important thing.
  3. See of my framework language is ideal? (in general it’s don’t realy matter).
  4. Begin!

Git

Rob Pike’s 5 Rules of Programming

  1. You can’t tell where a program is going to spend its time. Bottlenecks occur in surprising places, so don’t try to second guess and put in a speed hack until you’ve proven that’s where the bottleneck is.
  2. Measure. Don’t tune for speed until you’ve measured, and even then don’t unless one part of the code overwhelms the rest.
  3. Fancy algorithms are slow when n is small, and n is usually small. Fancy algorithms have big constants. Until you know that n is frequently going to be big, don’t get fancy. (Even if n does get big, use Rule 2 first.)
  4. Fancy algorithms are buggier than simple ones, and they’re much harder to implement. Use simple algorithms as well as simple data structures.
  5. Data dominates. If you’ve chosen the right data structures and organized things well, the algorithms will almost always be self-evident. Data structures, not algorithms, are central to programming. Pike’s rules 1 and 2 restate Tony Hoare’s famous maxim “Premature optimization is the root of all evil.” Ken Thompson rephrased Pike’s rules 3 and 4 as “When in doubt, use brute force.”. Rules 3 and 4 are instances of the design philosophy KISS. 5 was previously stated by Fred Brooks in The Mythical Man-Month. Rule 5 is often shortened to “write stupid code that uses smart objects”.

API Development

  • Use overapi
  • Avoid creating your own components for functionalities like keyboard navigation or swipe gestures. Use libraries such as Radix UI instead.