Yea. Trump even pardoned a special forces killer against the wishes of fellow vets, the military, etc. our respect for veterans is flimsy.
1,986 karma · joined November 30, 2010
RLS is difficult to unit test, to configure with flags, not portable to secondary stores, and requires knowledge of arcane database features.
When you put some private data on a cache somewhere and query it, now you need to write your access layer twice since the other one is so tightly coupled to the database.
The same “dice roller” in the sky that brought me trauma also brought me a high affinity with math and science, some pathway to a great tech career so acknowledging a higher power is really about saying “shits gonna happen, good and bad”
Edit:I guess I should have qualified that I’ve only done support groups in SF that have been great and usually hosted by churches.
Once I ejected it took a little hacking to get the index.html to work with handlebars cause I like to render a bunch of data and other stuff server side for speed optimizations.
Now I use the same web pack pipeline CRA ships with and just point my server to serve static files from the build folder. I’ve removed the server component and now just have the script watch and build. I don’t believe in SSR for react and prefer handlebars for most things server side so this workflow suits me well.
The product makes you feel like it’s a one click thing but you need to check in with a lawyer to not forget anything. Most ppl who used Atlas have told me the same. I do recommend Atlas since you will save some money and you get some nice fringe benefits.
Unfortunately, if you even think about your attorney, you'll be charged for it but the peace of mind is worth it.
Having a lawyer you trust, is timely to questions, and works fast is just a layer of stability you need so you can focus on the important parts of a startup. Legalzoom is garbage in this regard.
Unless your Uber and than a lot of those folks got fucked. Shrug.
Systems, networking, databases, machine learning have fantastic resources available. I usually look up the syllabus of a course at Stanford or MIT and check out their recommended reading. Some professors publish their own books for free as PDFs as well.
Women working is a way of evening out the power imbalance that has led to suffering for women all over the world since the beginning of time.
When you have no economic power you are dependent on your husband which is why unpaid labor is so dangerous. The husband calls the shots. Not all husbands are good guys. It's only reasonable for women to want to reduce their exposure to this problem via things advocated for by feminists over time: birth control to avoid unwanted and forced pregnancies (far more common in the days of having 5+ children) and of course death during childbirth, literally their own income stream so they can pay for things a husband might not value equally: healthcare, tuition, clothes, and more, an income stream to enable a divorce should the husband be an abuser, problematic addict or worse...
in less shitty scenarios, the sudden death of a male partner can result in financial ruin for a family with a 'non-working' mother. Again, its economically reasonable for a woman to want to hedge against being stuck at 40 years old with no advanced skills in a career.
It's all about female empowerment.
The weird thing for me is how trapped I felt by my vest dates before leaving the comfort of a well-funded business. I could afford vacations and clothes I wanted, if I waited long enough and kept getting promoted I could eventually buy an overpriced but lovely home in the Bay Area somewhere but I'd never have enough money to really live free.
Do I regret leaving to start a company and ultimately fail? No. I used to be poor and I got used to being poor again. Leaving the island was awful however: paying for food and healthcare again, an inability to enjoy the myriad distractions of the bay. I might never be able to afford a home of my own but I'm lucky that my wife is an artist and is happy to entertain the struggle as well. I'm actually on company number two but this time with some funding.
It's a hero's journey, like the odyssey or wandering the desert. I somehow have found peace with all this; the debt, the fear, the stress. The journey itself is the reward even if it is a bitter one.
What I'm saying is, if you get the sense you don't want to be a lotus eater in Silicon Valley, say fuck it and pull the plug. You'll grow some scars, it will absolutely suck (even my peers who did YC feel this way), but you'll feel some kind of cosmic satisfaction with your path like Odysseus.
And if you don't gain that peace, you can always get another job :)
https://www.theatlantic.com/technology/archive/2017/05/echo-...
> In the intervening decades, Echo has never changed its primitive interface. To navigate within it, you can’t just click on links, but have to type in Echo-specific commands: j cen; l a m; sh 123. You don’t access it in your browser, but through a telnet client, a program that allows you to access the command line interface of another computer. It doesn’t support images or sound, much less video. It doesn’t even have colors. It’s text-only, and even editing text is a time-consuming pain in the ass.
The scaling needs, technically or culturally, of a company at this stage are unlikely to be available at a risky early startup that may never see massive growth. At a BigCo, unless you are in infra or deep in the technical stack, many of these scaling problems will have been solved for you.
In terms of networking, you will get to learn from grizzled engineers who were around in the early days, veterans from big companies who have come in to fix the shit that is wrong, and have a front seat to these cultures colliding. Not only that, you'll be surrounded by soon to be angel investors.
I spent one year working at a pre-IPO unicorn and it was highest in ROI for my career as an entrepreneur later and the IPO made me enough cash to not be sweating my rent all the time.
Companies may have really good reasons to break old APIs. I’ve done this before...retiring an old framework and set of APIs that was inherently much less secure than what the bulk of customers needed.
Outside of the Bay Area tech scene, I can't imagine I would ever use LatinX in Spanish conversation. I choose my battles.
I'm saying that any internalized biases, anxieties, etc are deeply personal whether you are of an in group or an out group. It's totally a mental thing for me to get psyched out in an interview so of course therapy helps.
It's deeply personal but it's also something I know anecdotally is common amongst my peers of similar background. I'm pointing it out as one of the ways an interview can be unintentionally biased.
It's not about an interview format for a different race but interviews that take into account how being the odd person out may make it harder than it needs to be. In my ideal process, that helps everyone have a better interview.
Plenty of white people are uncomfortable around minorities. Do they all love that feeling? I'm confident most feel intense guilt about it and never act on those impulses in any way. Just having a 'racist' feeling doesn't make someone racist.
It's ignorant to not realize that all of these things are mental. Duh, therapy helps. Trust me, every single person of color who works in tech and sees a therapist talks through all this stuff with their practitioner.