trias
Re:Germany Arrests 25 Suspected of Planning to Overthrow Government
on Thursday December 08, 2022 @03:08AM (#33905515)
That is what elections are for.
Apollo Guidance Computer
Re:Hooks are the best thing to happen to React
on Saturday October 23, 2021 @10:11AM (#28968691)
To me React hooks look like they want to be a different programming language while still using js-syntax. It would be great if "useState", "useMemo" and the like would be first class citizens in a PL.
Hooks as they are have some non-obvious rules which can make them hard to understand / learn. Also debugging is not great (but that's true for react in general, imo)
Re:MacBook Pro 14-inch and MacBook Pro 16-inch
on Monday October 18, 2021 @02:44PM (#28909637)
what happened in 2013?
Re:Exploring Clang/LLVM optimization on programming horror
on Tuesday August 17, 2021 @06:28PM (#28215531)
is complexity theory constrained to binary representations? Why should it?
Chicago Reversed Its River
Re:Java JDK 1.0 (1996)
on Saturday May 15, 2021 @07:28AM (#27164290)
https://github.com/ufuu/JDK10/blob/main/src/src/java/util/Da...
> private int tm_year; /* years since 1900 */
when you have 4.3 billion years to choose from but decide for 1900.
Re:Efficiency Is the Enemy
on Tuesday May 04, 2021 @11:23AM (#27038566)
I agree totally. It matches my learnings in my career as well. But how much slack is the right amount? What do you think?
Re:Thanks for the Bonus, I Quit
on Sunday April 18, 2021 @04:25AM (#26850771)
I've made the opposite experience (in germany). No company will ever fire anyone. If they really need to, they give you a generous leaving package. The only exception is if the company going bankrupt, in which case the state might help (Kurzarbeit or bail out).
Re:On navigating a large codebase
on Sunday February 14, 2021 @12:39PM (#26134288)
sounds like we are working at the same company ;)
Good to see that this approach seems to be working for you, i wish you the best.
Re:On navigating a large codebase
on Sunday February 14, 2021 @06:56AM (#26131612)
sounds like an ideology lock-in. Let's hope you never get a problem which does not fit your current architecture well, or else you'll end up spending weeks or even months solving an otherwise trivial problem.
I've worked with "configuration-based implementations" and in my experience they are hard to work with (no debugging, incomplete documentation and implementation, little flexibility), require an staggering amount of infrastructure, are hard to test and will approach a programming language over time.
Extracting Training Data from Large Language Models
Re:Evil Unit Testing (2019)
on Thursday September 24, 2020 @03:25PM (#24582512)
not just warranted, the (2019) is very misleading.
Re:No Hello (2013)
on Friday August 21, 2020 @08:25PM (#24240423)
no, just communicating with my coworkers.
Re:No Hello (2013)
on Friday August 21, 2020 @08:24PM (#24240412)
that's an unusual style of communication. You are coworkers. If you don't know the answer immediately, say it.
Consider too, that i might be blocked as long as i don't have an answer.
Re:No Hello (2013)
on Friday August 21, 2020 @08:14PM (#24240337)
I dont expect an immediate reply, just within reasonable time. I i've made the experience that a question you ask upfront simply gets ignored and then forgotten.
Re:No Hello (2013)
on Friday August 21, 2020 @07:57PM (#24240199)
if you write "hello" and they answer "hello", they are under some social obligation to answer rather promptly, whereas if you write your question first, it may simply get ignored. So I tend to write a short hello first.
possibly some other social factors at play here, but still, my experience.
Re:Wirecard files for insolvency after financial hole laid bare
on Thursday June 25, 2020 @03:16PM (#23644377)
At some point you start believing your own lies so he probably thought everything would be fine and the markets would be calmed with another auditor confirming the results.
Excessive line breaks are bad
Living Root Bridge
Re:Deno: JavaScript Runtime for V8 Written in Rust
on Monday January 20, 2020 @07:28PM (#22103247)
- no file system access
- no internet access
- no environment access
also loads code from the internet and runs it no questions asked.
Re:94k Bitcoin (1B USD) transferred from unknown wallet to unknown wallet
on Monday September 09, 2019 @02:33PM (#20920925)
Bitcoin is inflationary, as there is new money created every 10 minutes or so. Wether it increases or decreases in value relative to the USD is subject to speculation regarding the expectations of the "demand" of bitcoins, which are certainly not stable. USD on the other hand is much more stable regarding inflation or deflation.
Re:JavaScript: The Modern Parts
on Saturday August 24, 2019 @06:51AM (#20786444)
> majority of js developers that take surveys
i like that qualification :)
most likely typescript is still a very small minority given how large the javascript world is
Re:Yield curve is blaring loudest recession warning since 2007
on Monday August 05, 2019 @02:05PM (#20616560)
Well in the case of stacks, the expected dividend (price of the eggs) also dropped by half. So yes, you really are poorer when you bought those expensive hens compared to someone who buys them at the reduced price.
Re:Better Portable Graphics
on Saturday July 13, 2019 @03:46AM (#20427002)
They are developed in switzerland
Re:Why Continuations Are Coming to Java
on Tuesday July 02, 2019 @07:16AM (#20333951)
i know, but why doesn't the OS do this too? Most programmers don't care if their "thread" is an actual thread on the machine or just a "fiber". If the benefits are this large, it should be provided by the OS in my opinion.
Re:Why Continuations Are Coming to Java
on Tuesday July 02, 2019 @06:34AM (#20333790)
Honest question, maybe obvious: Why is the java-scheduler/ thread model so much better than the OS-level one? What does the java one do, or better what does it not do? And why can't the principles which make java-scheduling fast be applied to OS-threads?
Mosuo Women
Re:What's next for SemVer
on Monday February 11, 2019 @05:09PM (#19138853)
Is there something like "test-driven versioning"?
It would be rather simple: "Here is the testsuite for our (public) api. We support the use cases tested, but no more.
If you want your use case covered, please submit a testcase.
If we change an existing test, we increase the major version.
If we add tests, we increase the minor level.
If the test suite remains the same and we only change the code, it's a patch-level increase."
This could be verified automatically, increasing trust.