It was probably 7 years old by then, so I just got rid of it. After about a year, it stopped turning on. I used it to read about 75% of Orson Scott Card's novels within the Ender's Game series. For fixed layout magazine/comic/manga where the entire file can be 100MB or more, this helps a lot.Ī friend sold me an original kindle for maybe $20 one time. This allows you to start reading image-heavy book quickly, while images continue to load in the background. The new KFX format has one major advantage over EPUB. Moreover, KEPUB and EPUB on Kobo use different renderer (EPUB use RMSDK, KEPUB use Kobo's own) with different supported features. Its native format is KEPUB, which has tons of id-tagged inside the content. I actually just realised yesterday that Moon Reader+, one of the best epub reader for Android, doesn't support vertical-rl layout (mostly used in Japanese book).Įven Kobo doesn't use EPUB as-is. I don't think anything (except maybe Adobe Digital Edition) support everything. I think there is actual technical reason why Amazon don't adapt EPUB natively (the Kindle Direct Publishing accept EPUB as input for ages).ĮPUB has a lot of features. I always see people saying these kind of thing about Amazon, but personally, I don't think this is the case. I could go on and on, but I feel anxiety right now even thinking about my time working there. You can pay H1Bs less, and they’re happy with it because they get to live in Redmond, WA instead of India. They refuse to hire or even interview white, black, or Hispanic candidates. Kindle was an army of H1Bs with an extremely toxic culture. Now you can just move on to AWS (or find another team in any of Amazons legacy businesses where you can coast). You were in Kindle and this new piece of shit has made on call hell? Oh well, you already got your promotion. Then, you simply just move onto to another organization. If this is someone else’s idea, you’ll do whatever it takes to take credit when this succeeds but blame everyone else when it fails.īest case, the thing you deliver gets you promoted. This is your ticket to getting to the Principal level. You’re careful not to write much of the code and mainly come off as being the architect and consultant. For an L6, you spend your time selling the absolute hell out of this thing, going on a road show and pitching your idea to get buy in from other teams. For L4s and L5s, it’s your ticket to the next level. If you’re a developer, you flock to the same project. It’s their ticket to a director promotion. There’s an OP1 document, where an L7 writes a fancy narrative, justify more head count and growing their organization. These are narratives where they spend hours and hours reviewing and nit picking how “crisp” a sentence is, or how there are too many commas, or some other superfluous bullshit. Then, I can claim a larger scope and significant impact, no matter how pointless, costly, or annoying this thing is to customers. > I’m going to build a new framework, platform, format, or some other “thing” that everyone should now use to solve. This is not only SDEs, but L7/Senior engineering managers and L8/directors, who latch onto a sales pitch and put all their eggs in one basket. Rather than solving real customer facing problems, many organizations including Kindle, emphasize “what do I need to do to get promoted?” This rings true across product management and software development. This article brought back memories of my time working in Kindle.Īmazon has a culture of promotion focused “engineering”.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |