skydhash

7 ms·

151.
by skydhash 2mo ago
> and it was pretty much trivial to spit out support not just in gcc and llvm, but I also, for fun, made WATCOM backends and a few other things No links? You may have dreamt about it instead.
152.
by skydhash 2mo ago
Rat race is the perfect term. In most of my contract job, I got laid off because product couldn’t come with an idea for a feature. Current prod was running well, a bug every once in a while when we hit an edge case, bug that is resolved wit
153.
by skydhash 2mo ago
> The whole 'its only predicting the next ___' has got to die. Isn’t it the truth? Just like computers are mostly a lot of switching on and off. While we know the theory behind why we are switching things on and off, we still h
154.
by skydhash 2mo ago
> They will trivially add features that humans would have pushed to a backlog forever as not worth the effort. More features is always good, right? Let's build dropbox+gmail+netlify+spotify+youtube+hackernews+... \s
155.
by skydhash 2mo ago
> I do know we will never go back to mainly programming through code again, that’s for sure. Say who?
156.
by skydhash 2mo ago
So where’s the value in that description? Something that can justify the mania and size of investment we have currently?
157.
by skydhash 2mo ago
Then you may need to improve your git-fu (or $vcs-fu). I use magit, so it's always easier to select only the lines/hunks/files that is for one specific change, stage and commit that. Before magit, I use sublime merge, Intelli
158.
by skydhash 2mo ago
Pretty much this. In OSS, review is mostly about convincing the others that your change is good and useful enough to merge. In corporate, it's seen as a blocker to change the ticket status to done. The vibe of the latter is mostly &quo
159.
by skydhash 2mo ago
Writing a paper doesn't start with writing an abstract too, but no one wants to get hit with all the notes that a scientist has collected on his experiments. The abstract is a nice 10-30 seconds explanation on why this paper is worth r
160.
by skydhash 2mo ago
> A PR with a minimal title and empty description should be refused at submission Sometimes a title is all that’s needed, but that’s often related to the complexity of the change. I only bother with an actual description only when the (s
161.
by skydhash 2mo ago
Isn't it the one installed on a computer in Canada, that we wouldn't know of? /s
162.
by skydhash 2mo ago
When it was the policy to use AI tooling, that’s all I ever used. And it was mostly one or two prompts in most conversations to get things done. Get a first version generated by the AI and fix the issues manually.
163.
by skydhash 2mo ago
> Current timelines I'm facing are to be going from "thought", through customer trials and being fully live in the product and ready for sales in ~3 weeks (from kick off to live in app is a bit more than a week). This is f
164.
by skydhash 2mo ago
> I very sincerely doubt it is possible for even an incredible engineer to keep up with the delivery schedules required to ship products now. What's the current delivery rates? From my past experience, any feature can take several w
165.
by skydhash 2mo ago
> Last side note, when this topic comes up I feel some folks are really biking it down to the absurd "typing was never the hard part Compared to the other parts. If you can do the problem solving part and the design part,code is eas
166.
by skydhash 2mo ago
> And if they realize halfway through implementation that there is a better way to do it, but they are under pressure to deliver, they wont have time to rewrite it and will live with the consequences of that decision forever I've ne
167.
by skydhash 2mo ago
I'm more likely to have several tabs of the libraries/language docs open than opening Google. And when I do, it would be just a faster way to get to the docs. After a while in a project, my history and bookmarks list is much more
168.
by skydhash 2mo ago
We had version control in the 70s with SCSS and then RCS. They were primitive, but a lot of software were only a few files.
169.
by skydhash 2mo ago
> A good engineer, with a good model and harness will produce great stuff. A bad engineer with a good model and harness will produce something faster, but it will be worse. A good engineer, without LLM assistance, will still produce gre
170.
by skydhash 2mo ago
Pseudo SQL select l.id, l.name from locations as l where l.type = 'amusement_park' and exists ( select id from locations as l2 where l2.type = 'rv_parking' and distan
171.
by skydhash 2mo ago
If I have to describe the feeling is that you'll realize that computation is symbolic manipulation (yes, it is obvious, but quite difficult to be fluent in it). With C and the likes you're too close to the machinery to easily gras
172.
by skydhash 2mo ago
I still use the first strategy (with DDG) and it still works great. But for technologies I work often, I just take a bit of time to familiarize with the site's structure and maybe bookmarks a few pages.
173.
by skydhash 2mo ago
There’s a lot of patterns in TUI due to slow terminals that can be reused, especially with full/half page scrolling instead of line by line. And like less and emacs (vim may have that too), the full screen scroll may be minus a configu
174.
by skydhash 2mo ago
Still the six month wait time when everything should be good? /s
175.
by skydhash 2mo ago
I’ve been burned by this enough that I no longer say that I’ve learned something if my only interaction with it is explanation from books. You can get snippets of knowledge and a framework of understanding, but true learning only comes with
176.
by skydhash 2mo ago
Moving up and down the layer of abstraction is an orthogonal skill. The skill I’m talking is taking some axiomatic concepts (can be opcodes or functions from a high level DSL) and then build something using the given rules. I took basic alg
177.
by skydhash 2mo ago
If you’re struggling at formal thinking, coding will be hard for you. I’m not talking about designing software with higher concepts, like thread, network IPC, web application routing, gui,… but more simpler one like basic data structures (l
178.
by skydhash 2mo ago
Those computing ideas (like distributed systems, concurrency and task scheduling) can even be found in even a single program/system. They are often entangled with even broader concepts, like visual layouts, security (authentication, au
179.
by skydhash 2mo ago
I think most do. You often sees that OSS often provide a disclaimer that they’re not liable for damages. You can’t easily do that when you provide a paid service. B2B often have SLA contracts that usually keeps everyone on their toes and no
180.
by skydhash 2mo ago
It’s pretty simple. Both the intake and the output of the LLMs are data and they shouldn’t drive an actuator system (their output shouldn’t be instruction). We already have the same structure in organizations where there’s an army of analys

More ›