Skip to content
View daltonfury42's full-sized avatar

Block or report daltonfury42

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
daltonfury42/README.md

Hi there 👋

I'm a Backend Engineer based in Bangalore, India.

  • 🏢 I'm currently working full-time with awesome peeps in an early stage startup.
  • I am one of the maintainers of SimplQ.me, an open source crowd control platform.
  • 💬 Feel free to reach out to me for pro bono consulting and volunteering, or just for some interesting discussion over here.

fury's GitHub stats

Rob Pike's 5 Rules of Programming

  • Rule 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.
  • Rule 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.
  • Rule 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.)
  • Rule 4. Fancy algorithms are buggier than simple ones, and they're much harder to implement. Use simple algorithms as well as simple data structures.
  • Rule 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. Rule 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".

Pinned Loading

  1. SimplQ/simplQ-frontend SimplQ/simplQ-frontend Public

    Modern and fully web based free queue management open source software.

    JavaScript 176 135

  2. truecase truecase Public

    A python true casing utility that restores case information for texts

    Python 87 16

  3. EarningsCall EarningsCall Public

    The codes I wrote for earnings call project

    JavaScript 1

  4. RFID_Writer RFID_Writer Public

    A simple GUI to write to STA IR0507E Middle-Range RFID Reader.

    Python

  5. eXpOSNitc/eXpOSNitc.github.io eXpOSNitc/eXpOSNitc.github.io Public

    Website for Project eXpOS (eXperimental Operating System)

    HTML 19 17

  6. SimplQ/simplQ-backend SimplQ/simplQ-backend Public

    SimplQ backend, written in Java for AWS

    Java 17 27