Viewing profile — jongleberry
jongleberry
HN member- Joined
- Fri, Feb 24, 2012, 9:18 AM UTC
- HN karma
- 122
- Public activity
- 71 items
- HN profile
- View on Hacker News ↗
About jongleberry
No profile information was provided.
Recent public activity
-
comment
Comment #47880051
it seems to be the same cycle for everyone now, not based on first usage. I saw a reddit thread on this from someone who had multiple accounts that all had the same cycles
- comment
- comment
- comment
-
comment
Comment #27456940
I don’t know the details as I didn’t work directly with him, but from what I understand he was trying to get a sabbatical to figure out some life stuff, but eventually he had to qu…
-
comment
Comment #27456827
Which means you need to find a new employer. There are companies and/or managers out there that don’t have these misalign incentives, encourage best practices (like those in this b…
-
comment
Comment #27456734
we had a principal engineer who thought he was very skilled and held critical knowledge and tried to use it as leverage. turns out, everyone else considered that poisonous behavior…
-
comment
Comment #27456689
seems like you need to find a job with better management
-
comment
Comment #27456671
I'd agree on most points, but like others, 1 & 2 I don't agree with. Most of my knowledge is useless or irrelevant, so taking the time to document this knowledge is a waste of time…
-
comment
Comment #25907309
You can set up a GitHub Action that performs an action on any push to master/main (or any branch). You can also only perform the action when specific files are changed: https://doc…
- comment
- comment
- comment
- comment
- comment
- comment
-
comment
Comment #18295911
At Dollar Shave Club, we use CircleCI 2's Scheduled Workflows to run "monitors" against our production services every minute. These are idempotent, analytics-disabled API & Browser…
- comment
- comment
- comment
- comment
- comment
-
comment
Comment #13952864
I have this exact problem with Microsoft Azure as well. Changing pages always takes 5-10 seconds and you can't open in a new tab to open new tables concurrently. Makes working in t…
- comment
-
comment
Comment #11370784
My same thought as well. S3 has a rate limit, which is where a lot of these timeouts or errors are probably happening. Seems like they should be using a database instead.