He's getting downvoted, but he's not wrong - however, finding someone who specializes in doing this would be hard, and knowing how to word it so you can use "standard crews" would itself be $2-3k for a GC.
This is the danger of "cheap projects" - they can grow legs before you know it, and you end up paying half the cost of increasing the square footage of the house (or the garage).
Some things are deceptively complex (foundations and roof trusses come to mind) and the cost if you get it wrong can easily double the total cost of your build 6 months after you think you are done.
Walls, floors, ceilings and everything in between them are both less complex and cheaper to fix than foundations or trusses.
Unless he’s a commercial builder, I’d suggest he is wildly wrong about what is involved in properly pouring, leveling and making sure concrete has properly set in various weather conditions. And if you take a look at his post …
Tie::Hash::Cannabinol is a completely useless demonstration of how to use Tie::StdHash to
pervert the behaviour of Perl hashes. Once a hash has been tied to Tie::Hash::Cannabinol,
there is a 25% chance that it will forget anything that you tell it immediately and a
further 25% chance that it won't be able to retrieve any information you ask it for. Any
information that it does return will be pulled at random from its keys.
Oh, and the return value from exists isn't to be trusted either :)
There must be something fascinating about writing Markdown apps - either it scratches an itch, or AI is really good at creating them. There's a flood of them on r/macapps and similar places.
It's because it's effectively impossible to make a markdown authoring app that meets everyone's needs, and people tend to be picky about what they want in a writing environment. People have strong preferences about WYSIWYG, flavor of markdown (pandoc/quarto/GFM/etc), theming support, some want notes to be able to link to each other, etc. As an example, I require math notation support for basically everything I write which automatically rules out 90% of markdown editors for me.
All of this, but underlying it I've come to the conclusion that Markdown isn't a good format for a writing environment beyond just simple prose. There's too much left up to the flavour of it and it's got weaknesses.
I've been experimenting with using Markdown (in Typora) in place of Word, but it (and others I've looked at) have zero support for image positioning or sizing, or a way to have different (pre-defined) styles on different tables.
Which is a shame because I like keeping my documents in plain text, in version control and efficiently read by my LLMs. LyX (https://www.lyx.org/) for LaTeX is the closest to what I'm thinking of that I know of, but maybe something exists for Asciidoc or Typst.
I always have a hard time understanding why anyone would want a dedicated markdown editor in the first place.
Obviously I am not the intended audience for them, but for me markdown is a fundamentally plain text format, Make nice looking plain text, and if you keep to certain well known patterns, you get a chance to run it through a typeset engine. Most of the point being the plain text. If the point were the typeset document, I would pick a better language.
As such, the ideal markdown editor is a text editor.
a nice md editor feels good. when all the UI is out of the way it gives a minimalism feel and i start to notice tiny details like 'this font is really soothing' and thats where i imagine i want to put my markdown thoughts in. a pure interface
I suspect it's because there's a flood of people writing / looking at MD docs that never did before and want better tooling than is readily known to exist.
I think we're going to see a lot of dev-related tooling that traditional developers would scratch their head and think... who could this possibly be for, and why would anyone spend time making this...
And it's just because there's an entirely new class of people doing this kind of thing now.
I wrote my own wiki to use as a personal knowledge base to replace Dokuwiki because I wanted a simpler Markdown-based solution written in Python. I started it during the pandemic times and all of the code in there to date was written by hand. All of it was pretty easy except the CSS/layout parts which I'm just not very good at. It took months of free time to get it where I wanted.
I also recently created a day-to-day notes and daily planner app that's basically a bunch of markdown notes. I spent about a week of free time defining the problem, setting constraints, and refining with an LLM that wrote almost all of the code for me. I've been using it for months and it's working great.
The wiki uses Markdown because I browse it just as often as I edit and I appreciate some modicum of basic formatting. The daily notes app doesn't really _have_ to use markdown, I've just gotten accustomed to writing Markdown pretty much everywhere.
(These are on github, but I'm not posting the links here because I don't want to or care about promoting them.)
Writing is also a deeply personal exercise for many, and I can say from personal experience that the environment I write in, from the room/place I'm in to the color scheme of my editor, really matters sometimes.
I haven't found a need to build my own editor, but I can see how someone else would.
didn't know about that, but when I looked around, most of them were paid and just didn't really scratch the itch. this really starte as a simple editor for writing blog posts
Or because rollbacks (and release) are slower than flipping a flag.
I’d rather invest in the feature flag upfront so I can unbreak customers in 2min rather than telling them to wait hours for the rollback.
Why are rollback and release so slow? Because we’re deploying to 40+ availability zones world-wide, totaling many thousands of servers, and we don’t want to worsen the impact by doing an accelerated “everything-at-once” rollback.
You are definitely in the minority ;)
IMO the commute is the biggest problem with RTO - why must I spend >1hr of _my_ time going to/from an office when I can do the same work at home?
reply