elischleifer

7 ms·

31.
Analytics Solution for GitHub Actions. No Need to Run CI in the Dark(blog.trunk.io)
22 points by elischleifer 4y ago|14 comments
32.
by elischleifer 4y ago
Probably anything intentionally melting chemicals should come with built-in fume capture.
33.
by elischleifer 4y ago
If you're holding maybe you don't think you've lost money yet - but you spent a bunch of money on 0s and 1s and no one is going to buy those from you.
34.
by elischleifer 4y ago
The success of any initial offering will lead to long term dilution. If Donal Trump believes he can mint money from the sky - then he will do that until this grift ends.
35.
by elischleifer 4y ago
Maybe HN should ban any site that isn't proffering a valid SSL certificate - highscalability.com.
36.
by elischleifer 4y ago
FWIW - we run secret detection in our trunk check precommit action - so we make sure that secrets are never committed into local or remote branches.
37.
by elischleifer 4y ago
I think it depends on what kind of technical writing. Are you interested in creating technical content for the outside world or content for internal consumption only. Do these individuals have strength in regular comms but trying to balance
38.
by elischleifer 4y ago
I hear you. But nothing goes directly into main. The working branch is not sacrosanct you know what I mean? I'd rather clean up anything that leaks in before merging and a good .gitignore can protect against most noise.
39.
by elischleifer 4y ago
"The information superhighway" - great callback. I love the scan lines running across the CRT as she's talking in the opening clip.
40.
by elischleifer 4y ago
This story is gross and not entirely surprising. It is unclear to me why anyone would stick around inside the other Musk co. @twitter that wasn't bound by H1B handcuffs. The upside in that company is really not there...at least at Spac
41.
by elischleifer 4y ago
I used to use CLion at my previous gig - before moving to eclipse and finally doing everything all day long in VS Code. I wonder if the performance issues of CLion have been addressed or if its still a performance dog.
42.
by elischleifer 4y ago
makes sense. thanks
43.
by elischleifer 4y ago
This disease is just absolutely devastating; I remember reading over the past couple years how the connection between protein buildup and alzheimers was being questioned more in the research. When a momentous breakthrough is a 25% delay in
44.
by elischleifer 4y ago
Congrats to the CodeCov team. Sentry is a fantastic operator/tech/business. Excited to see what unified features fall out of this purchase.
45.
by elischleifer 4y ago
I think the articles related to staff cuts should often call out what the company size was 12/24 months prior. It's never good for folks to lose their jobs, but companies, especially tech focused ones - grew unbounded during the l
46.
by elischleifer 4y ago
What's the pitch here? What makes this offering distinctive to JS developers vs any other species of engineer?
47.
Minimum Viable Git for Trunk-Based Development(blog.trunk.io)
48 points by elischleifer 4y ago|44 comments
48.
by elischleifer 4y ago
price predictability is super important in this space. usage based metrics are straight forward to understand around AWS. Burn more machines...cost more $. that equation is easy to understand and predict for. systems where the utilization o
49.
by elischleifer 4y ago
don't worry during the migration another new amazing fx will hit and you'll already be using the old legacy thing.
50.
by elischleifer 4y ago
I love the Iron Man reference. Everyone is always chasing the shiny new thing. Since my company build devtools the shiny thing is the thing that usually gets rusty - which is kind of the whole point I guess.
51.
by elischleifer 4y ago
100% - documentation will always go stale. the source of truth is the code however, and making sure the code is kept shiny is the primary task of engineering. documentation is non-load-baring - you can tear it all down and the project will
52.
by elischleifer 4y ago
there are bots that can resolve this one angle of the problem. they have drawbacks that are great opportunities to improve upon - dependabot loves spamming projects with update notifications and doesn't understand what its actually doi
53.
by elischleifer 4y ago
great point. I didn't see a mechanism for filtering out stale projects - if that is a GH concept inside CodeSearch. TLDR; there are a lot of active projects running rusty / rotten tools
54.
by elischleifer 4y ago
I joined MSFT in 2002 as the .com bubble burst. Microsoft was one of the few companies still hiring and building that year and it was a great place to cut your teeth and learn how to build software at scale.
55.
by elischleifer 4y ago
Congrats to the artemis team, but honestly this project is a testamount to the ridiculous inefficiencies in the government procurement process. Cost+ pricing and siting rules for manufacturing across constituent states led to a bloated anti
56.
82% of Open-Source Projects Suffer from Tool Rot(blog.trunk.io)
42 points by elischleifer 4y ago|58 comments
57.
by elischleifer 4y ago
software engineering is a constant fight against entropy. GitHub code search uncovers the scope of tool rot in open source projects.
58.
by elischleifer 4y ago
the only way you are likely to expedite processing of any bans/robo-blocks is to know someone on the inside of these companies who can try to expedite a review on your account status. that itself is a non-trivial lift.
59.
by elischleifer 4y ago
what! who would've guessed that Donald Trump was going to launch another bid for the presidency.
60.
by elischleifer 4y ago
It doesn't take much to trigger very bad things from escalating. Luckily comms are much more reliable now than when Arch Duke Ferdinand was assassinated. Also - no one wants to blow up the planet which is what a direct NATO/Russia

More ›