troyk
Joined 17 years ago
Joined 17 years ago
tldr; if it is sealed, do not worry about it. If not, be upfront as soon as possible.
Call the court clerk in the county the record is sealed in and confirm the record is sealed; If so, when a court researcher searches for the record, it will not appear and not be reported by the CRA (Consumer Reporting Agency is the technical term for a background screening company).
If you have never lived or worked in this county, it may never be searched.
If somehow the county reports the record and it is sealed, and the employer does not hire you because of the record, the employer has to do what is called the adverse action process, which gives you an opportunity to dispute the information before taking final action. During this time, you can have the CRA remove the record.
Enjoy hacking away at a FAANG!
<script>
import RedThing from './RedThing.svelte';
import GreenThing from './GreenThing.svelte';
import BlueThing from './BlueThing.svelte';
const options = [
{ color: 'red', component: RedThing },
{ color: 'green', component: GreenThing },
{ color: 'blue', component: BlueThing },
];
let selected = options[0];
</script>
<select bind:value={selected}>
{#each options as option}
<option value={option}>{option.color}</option>
{/each}
</select>
{#if selected.color === 'red'}
<RedThing/>
{:else if selected.color === 'green'}
<GreenThing/>
{:else if selected.color === 'blue'}
<BlueThing/>
{/if}Is brex a fit now, or in the near future?
psql is great for inspecting schema and running ad-hoc queuries. SQL scripts can also be piped through it for cron-sql jobs etc.
pg_dump + psql + ssh to easily copy databases between hosts
pg_bench for benchmarking.
Lots more: https://www.postgresql.org/docs/current/static/reference-cli...
No BS or bad vibes; Just real peeps writing code and having fun doing it and always looking to add great people to the team because the demand is high and experienced talent is in short supply.
We just interviewed a PM from HPE and to our surprise, he makes ~$180k a year. We hired an awesome candidate for $80k.
Except, we use postresql's LISTEN/NOTIFY which amazingly is also transaction aware (NOTIFY does not happen until the transaction is committed, and even more amazingly, sorta de-dupes itself!) to move the jobs from the database to the message queue.
This way we never lock the queue table. We run a simple go program on the postgresql server that LISTEN's, queries, pushes to REDIS and then deletes with a .25 second delay so we group the IO instead of processing each row individually.
This also allowed us to create jobs via INSERT FROM SELECT, which is awesome when your creating 50k jobs at a time.
Are there many winners with this model to name. Maybe NGINX, MongoDB?