969 karma · joined January 24, 2012
Maybe it's possible to force the transliteration to use a different allocator and then you could use the one you wrote in C?
I mean we deal with daylight saving time all the time and I know it's not the same because the leap second affects UTC, not just local time zone, it's just that you are either dealing with monotonically increasing time like epoch, or you are dealing with "human" time and I found no distinction in the latter.
Is it "just" that leap seconds or delay seconds caused problems in epoch to utc conversion? Note the just in quotes, but did I just answer my own question? :)
My gaming preference is to go to an area as per game design, so the fact that I would be outmatched does not bother me and would prefer it that way. I do, however, understand why the game designers chose level scaling for what they wanted to achieve.
I have to say I find it pretty funny.
In other words, they seem to achieve better results with smaller brains than we thought. And yes, crows (in EU) do exhibit some pretty intelligent behavior.
It might have been you, a couple of months later, or someone else. I have dealt with slop produced by unknowing programmers most of my career. With this vibe coding I think my job is still safe. The amount, though, is increasing exponentially.
It was about knowing how to fit the new use case into an existing code base, respecting the architecture, and sometimes rearchiteting the solution. How easy the latter was is really dependent on whether the code/arcitecture respected the low coupling, high cohesion principle.
Now, some of this can be coerced into LLMs but it takes work and careful study of the changes. Sometimes they get it right, many times they do not. So, you have to go back and forth with them. If you know what they should have produced.
SWE is far from dead. We just let too much slop into the codebase because we're overwhelmed by it and not incentivized by leadership to care. Code quality will likely drop to the point where even the leadership will notice and it will normalize again. There's nothing like a high profile customer calling out a problem that was vibe coded. It has started already and will be happening more and more.
Don't worry, the hype will be over in some time.
It's inevitable in childhood, but the parents' role is to create an independent individual. This often not the case, so we see ourselves in need of validation from our spouses, bosses, etc. and it can cause people to stay in bad working or personal relationships.
The trick is to be proud of yourself in an all-encompassing form, admit where you are not good at and improve, if you want to. Advice is welcome but critique should not lessen how you feel about yourself.
Just my 2c and what my experience in life taught me.
Of course, if a student just breezes through it then I would agree. That would make no sense.
Frankly, though, I think lispy community has benefited from being smaller. For example, even though the now ancient Design Patterns already warned programmers to prefer composition over inheritance, the OO programmers still created 15 levels deep hierarchies.
That said, in my country (in EU), it's not indefinite tries. The fourth and later attempts (up to 8, I think) have oral exams in front of a panel of professors so that they can evaluate if there is actual lack of knowledge or if there is some sort of problem between the student and the professor. The student must by then pay for the attempt to pass the exam. It's not expensive, though, it's just another incentive to make the student really be sure to be prepared.