blinkymach12

7 ms·

1.
by blinkymach12 8mo ago
https://www.allred.nyc/
2.
by blinkymach12 11mo ago
The struggle I found in coding as a CTO was that executive team priorities would come along that would take precedence over my ability to maintain my coding contributions, and in my experience no developer team wants to inherit and maintain
3.
by blinkymach12 1y ago
I don't think anything requires a README.md to be monolithic. They often provide the introductory material that you mention here, then link out to other appropriate files for contribution guidelines, etc.
4.
by blinkymach12 1y ago
I like this insight. We kind of always knew that we wanted good docs, but they're demotivating to maintain if people aren't reading them. LLMs by their nature won't be onboarded to the codebase with meetings and conversations
5.
by blinkymach12 1y ago
I don't think the bar here is a human level coder, I think the bar is an LLM which reads and follows the README.md. If we're otherwise assuming it reads and follows an AGENTS.md file, then following the README.md should be within
6.
by blinkymach12 1y ago
We're in a transition phase today where agents need special guidance to understand a codebase that go beyond what humans need. Before long, I don't think they will. I think we should focus on our own project documentation being co
7.
by blinkymach12 1y ago
I had the same thought as I read this example. Everything in the AGENTS.md file should just be in a good README.md file.
8.
by blinkymach12 2y ago
I like it! I spun up a little remixable Glitch project based on your demo so that I could play with it in a web editor. Thanks for sharing. https://glitch.com/~fullsoak
9.
by blinkymach12 2y ago
Thanks! Publication was February 2024.
10.
Carbon emissions of writing and illustrating are lower for AI than for humans(nature.com)
3 points by blinkymach12 2y ago|2 comments
11.
by blinkymach12 2y ago
I'm very much an environmentalist and am very concerned about climate change, and I feel like this article completely put me at ease about sea level rise. I suspect this was the opposite of the intent. I feel like in comparison to inte
12.
by blinkymach12 2y ago
I also had that impression. The headline worked for me, and then it sort of teased me along with details that ultimately ended without a conclusion and a feeling of "why did I just read this?"
13.
by blinkymach12 3y ago
From memory and a little grepping of the Weekly Kiwi archives, I found: "Project Null Terminator", Aardvark, B??, Caribou, Dingo, E??, Flying Fox, Giganotosaurus, ??
14.
by blinkymach12 4y ago
Aardvark'd: 12 Weeks with Geeks[1] is a delightful time capsule of 2005 software development. It includes interviews with @pg, the Reddit founders, and other delights. It's available on youtube now. When I interviewed at Fog Cre
15.
by blinkymach12 4y ago
FogBugz's evidence-based scheduling always resonated with me too. Back in grad school I remember writing a paper arguing how it was a fundamentally better way to manage project estimates and schedules. Curiously, even at Fog Creek, som
16.
by blinkymach12 4y ago
Fog Creek renamed to Glitch as we transitioned from being a bootstrapped product-incubation lifestyle company to a single-product VC-backed startup. I think of the Fog Creek storybook closing with that rename, since Glitch always had a very
17.
by blinkymach12 4y ago
- HyperWeb [ Internal project name for first ~year ] - HyperDev [ First public branding / early launch ] - GoMix [ First major relaunch, now with Anil as CEO ] - Glitch [ After acquiring the sweet glitch.com domain from the kind f
18.
Log4Shell, as Explained by Metaphor and Memes(medium.com)
2 points by blinkymach12 5y ago|0 comments
19.
by blinkymach12 5y ago
Thanks for sharing, Chris. Honestly it sounds to me like you're living the dream-- you're secure enough in your abilities that you can pursue the projects you're excited by rather than having to play career games as an employ
20.
by blinkymach12 5y ago
Hey Patrick! Thanks for the article. "Producing Artifacts" is definitely what we called that at Fog Creek, and I think our cousins at Stack may have used a different term but followed much the same spirit. I didn't realize u
21.
by blinkymach12 8y ago
Same.
22.
by blinkymach12 9y ago
Ah, good find of the github link! I imported it into glitch so I could see it run: https://honey-climb.glitch.me/
23.
by blinkymach12 10y ago
Fog Creek Software | Site Reliability Engineer | New York, NY | ONSITE, VISA, https://www.fogcreek.com/jobs/SiteReliabilityEngineerNYC Hi! We're looking for some SREs and Network Engineers to work with us in our
24.
by blinkymach12 10y ago
Thanks Blake! :-)
25.
by blinkymach12 10y ago
Fog Creek Software | NYC or Remote | System Administrator Fog Creek Software is looking for an experienced, unstoppable System Administrator. On our team, you'll work with top-notch developers and support engineers on the infrastructur
26.
by blinkymach12 11y ago
Fog Creek Software | HQ in New York City | Full-Time | Onsite, Remote, and Ad-Hoc Remote friendly. Fog Creek Software is a small, friendly software company in New York City that was designed from the ground up to be a great place to work. W
27.
by blinkymach12 12y ago
Fog Creek Software, New York City - REMOTE and in-office Hiring Developers, Designers, Support Engineers, and a Product Marketing Manager. Fog Creek Software is a small, friendly software company in New York City that was designed from the
28.
by blinkymach12 13y ago
These are excellent, well done! Thanks for both documenting your progress and taking the time to inject character into your games.
29.
by blinkymach12 13y ago
Hi dlp211, My name is Jude and I'm one of the developers at Fog Creek Software. I'm obviously a bit biased, but I'd be happy to talk to you if you have any questions about Fog Creek. Feel free to ping me at jude@fogcreek.co
30.
by blinkymach12 13y ago
Fog Creek Software - New York City - Trello Mobile Designer http://www.fogcreek.com/Jobs/TrelloMobileDesigner.html Fog Creek Software is a small, friendly software company in New York City that was designed from the gr

More ›