MTA (think trains and buses) | Full-time | NYC | 3x/week in office
We're looking for two frontend software engineers! (Interviews are starting this week, we're very ready.)
Our team works on all the (non-ad) screens in the subway, as well as two apps (TrainTime and the MTA app) and our website. We're a team of 20, mostly engineers, a few PMs and a designer. We operate like a startup within the MTA and are responsible for all customer-facing digital endpoints.
Homework before hand is an anti pattern IMO. It assumes people aren’t busy in the rest of their day and the meeting scheduler is inflating the toll of the meeting with a hidden prep tax. This is how people end up with 12 hour days.
Bezos forbade pre-meeting homework at Amazon for this reason. He was having a hard time keeping up with everything and the meetings were basically people recriminating each other for not being prepared then having to take up the first part of the meeting with catching everyone up anyways. So he structured meetings at Amazon as an introductory period of reading so everyone was always on the same page once discussion began. No slideshows, just reading a document of n pages where n is less than 6.
I personally find the high level IC pseudomanager role sad. I went back to IC to be closer to the metal. But the expectation is I’ll be a product manager, program manager, and people manager all in one while the focused roles work in a self limited silo.
Whenever this comes up, I think of this quote from The Practice of Programming by Brian W. Kernighan and Rob Pike [0]:
> As personal choice, we tend not to use debuggers beyond getting a stack trace or the value of a variable or two. One reason is that it is easy to get lost in details of complicated data structures and control flow; we find stepping through a program less productive than thinking harder and adding output statements and self-checking code at critical places. Clicking over statements takes longer than scanning the output of judiciously-placed displays. It takes less time to decide where to put print statements than to single-step to the critical section of code, even assuming we know where that is. More important, debugging statements stay with the program; debugging sessions are transient.
I found this lines up with my personal experience. I used to lean on interactive debuggers a lot, and still enjoy using them. They're fun and make for good exploring. But the act of figuring out where you want to print really makes you think in ways that interactive debugging cannot. I find the two forms really complement each other.
>We can see that not all obstacles make you stronger. Destroy the cartilage in your knee, and it may never fully recover, since cartilage doesn’t grow back. //
I'm not a medic but I recall this being disproven or shown to be at least partially a myth a few years ago - https://physicians.dukehealth.org/articles/humans-have-salam... from 2020, for example. Researchers showed that ankle cartilage is younger than knee- and younger still than hip cartilage. Indicating that it grows back in ankles relatively quickly.
As the article says, analogies can mislead us, but this didn't inspire confidence.
I could probably dismiss it if the article weren't about being scientifically precise and dispelling myths relating to human biology.
Good piece, but the title is misleading too as the conclusion appears to be "it's complicated; yes and no".
Create a folder on your computer or get a sturdy box made of good cardboard with a lid. Name the folder “Process”. Write the word “Process” on the box.
While working, occasionally take photos or screenshots of what you are doing showing your workspace, the computer desktop, the desk with pencils and papers and cables everywhere, the wall or piece of string with notes. Show the messy process of creating something.
Type notes on text files and save them with a name like yyyy-mm-dd-note-title.txt. Write notes on bits of paper and notebooks and journals with pencils and pens that you keep all around the places you spend most of your time in, including within arms-reach of where you sleep.
Practice writing down notes on a piece of paper in the dark, so you can do so when waking up in the night, before daybreak, to jot down thoughts and ideas from dreams.
Record messages and melodies using your pocket computer and remember to save these in your Process folder, too. You are looking for your voice.
Put these digital and physical notes in the Process folder and in the Process box.
Thank yourself later, in years to come.
You are what you observed. Experiences, memories, stories to be told. Put your marker on the map in time, that others may find and learn from.
Here's a query for a rough reproduction of what's asked in the title:
WITH whoishiring_threads AS (
SELECT id FROM `bigquery-public-data.hacker_news.full`
WHERE `by` = "whoishiring"
AND REGEXP_CONTAINS(title, "Ask HN: Who is hiring?")
)
SELECT FORMAT_TIMESTAMP("%Y-%m", `timestamp`) as year_month,
COUNT(*) as num_toplevel_posts
FROM `bigquery-public-data.hacker_news.full`
WHERE parent IN (SELECT id FROM whoishiring_threads)
GROUP BY 1
ORDER BY 1
There are supplements, backed by research, that practically remove all of the negative side effects of adderall. To start with, the sadness you felt on vyvanse sounds like dopamine depletion. You want to be taking l-tyrosine to make sure there’s plenty of fuel for the amphetamine to work with. ALCAR + ALA counteract the psychomotor agitation and tolerance formation. Magnesium + zinc help with muscle cramping. Selenium is neuroprotective. And of course you want to make sure you’re getting enough electrolytes (sodium + potassium) and balancing your intake, as a general rule for life, but especially if you take stimulants.
With the aforementioned supplement stack I’ve been able to go off doses as high as 60 mg of adderall per day without any significant withdrawal symptoms. It’s been a complete game changer in terms of making this medication a sustainable option for me. I will say as a caveat that things which reduce drug tolerance formation also typically attenuate some of the effects. In my case, ALCAR + ALA basically erase the potential for euphoria but don’t seem to diminish the mental benefits.
We're looking for two frontend software engineers! (Interviews are starting this week, we're very ready.)
Our team works on all the (non-ad) screens in the subway, as well as two apps (TrainTime and the MTA app) and our website. We're a team of 20, mostly engineers, a few PMs and a designer. We operate like a startup within the MTA and are responsible for all customer-facing digital endpoints.
See one of our products here: https://apps.apple.com/us/app/mta-traintime/id1104885987 as well as some new screen designs here: https://www.reddit.com/r/nycrail/comments/1h2rqr6/new_countd...
Job description and application details: https://www.mta.info/document/163661