Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content
View kislayverma's full-sized avatar

Block or report kislayverma

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

Pinned Loading

  1. Rulette Rulette Public

    A pragmatic business rule management system

    Java 96 27

  2. rulette-server rulette-server Public

    REST server + UI for Rulette

    Java 16 2

  3. qvertx qvertx Public

    Ready to launch service framework built on Vert.x

    Java 12 2

  4. A copy (for posterity) of Steve Yegg... A copy (for posterity) of Steve Yegge's internal memo in Google about what platforms are and how Amazon learnt to build them
    1
    I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
    2
    
                  
    3
    I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't really have SREs and they make engineers pretty much do everything, which leaves almost no time for coding - though again this varies by group, so it's luck of the draw. They don't give a single shit about charity or helping the needy or community contributions or anything like that. Never comes up there, except maybe to laugh about it. Their facilities are dirt-smeared cube farms without a dime spent on decor or common meeting areas. Their pay and benefits suck, although much less so lately due to local competition from Google and Facebook. But they don't have any of our perks or extras -- they just try to match the offer-letter numbers, and that's the end of it. Their code base is a disaster, with no engineering standards whatsoever except what individual teams choose to put in place.
    4
    
                  
    5
    To be fair, they do have a nice versioned-library system that we really ought to emulate, and a nice publish-subscribe system that we also have no equivalent for. But for the most part they just have a bunch of crappy tools that read and write state machine information into relational databases. We wouldn't take most of it even if it were free.
  5. throo throo Public

    A Vert.x/Spring based HTTP reverse-proxy

    Java 19 9

  6. go-crud go-crud Public

    CRUD service to learn Golang

    Go 25 5