1,557 karma · joined April 20, 2022
On the funding side, we have the Austria Wirtschaftsfond, which provides angel-level funding on some level, but the amounts are relatively low and there are restrictions what the money can be spent on. (E.g. only employees, which shareholder-CEOs are not in all circumstances, etc.) Basically, it's tricky and a jungle to navigate. I have never done a US startup, but from what I saw it seemed less intricate.
On the flipside, my wife and I have a GmbH and since we got over the initial unknowns, it seem relatively straight forward to actually run the company on a day-to-day basis, provided one actually makes money.
The result? I'm "ok". Apart from the current website I made with my wife, I mostly made relatively simple designs which I could at least look at. Theory really helps provide guardrails, rules to follow. Later you can stop following the rules once you know what you are doing.
Edit: I also find multiples very helpful. For a website, I'd start with a base line height of 1.5rem and make everything a multiple or divided by a whole. Menu height? 3rem. Border radius? 0.75rem. Padding? ... You get the idea. Later on you can bring in stuff like golden ratios. When I started 3D stuff, I did the same in Blender. I moved everything via the coordinate box.
At any rate, taking down the Blender website wouldn't help them I don't think.
Over the years I had several discussion to that effect and I truly, genuinely don't understand. I have test cases that test a connector to, say, Minio, so I spin up a Minio container dynamically for each test case. I need to test an algorithm, so I isolate its dependencies amd test it.
Shouldn't the point be that the thing is tested with the best tool available for the job that ensures robustness in the face of change rather than riding on semantics?
Taking things away as a method of enforcement doesn't seem to be all that effective and it undermines the kid's self determination. The only thing it does make kids angry and disappointed. A lot of kids have to live by arbitrary rules that don't make any sense, or if they do, haven't been explained to the kid. "Go to your room" and taking things away need to go away from the parenting toolkit, they just lead to kids who get accustomed to going behind the parents' back.
They can maybe compete in areas where there has been a lot of public discussion about a topic, but even that is debatable as there are other tasks than simply producing code (e.g. debugging existing stuff). In areas where there's close to no public discourse, ChatGPT and other coding assistance tools fail miserably.
Edit: wow, that's how I'm reading it too. If you have a DUNS number, this will presumably not apply to you. So this isn't about quality, it's an anti-spam measure. Crazy.
This is a problem because every time C has a vulnerability, you get a deluge of vulnerability scanner alerts or Dependabot pull requests to update it, even though your application has nothing to do with C.
If anyone has a solution for this, I'd really love to hear it because it consumes a silly amount of time to deal with bogus vulnerability alerts.
Apart from the obvious bandwidth and storage space wasted, this is also a problem when compiling an SBOM (Software Bill of Materials) and when scanning for vulnerable dependencies. There is simply no way to tell if your Go binary is vulnerable simply by looking at the go.mod/go.sum file, you have to build and analyze the binary and hope that everything went well. Same for compiling NOTICE files for license compliance. (wink wink Apache license)
This isn't an unknown or unsolved problem either, Maven solved this ages ago.
There are also some minor nitpicks, such as their absolute requirement to do path-based semantic versioning from v2, but not from v1 or v0. If you change anything, but absolutely anything that's publicly visible, you must increase the minor version of the library you are publishing or you will have a really bad time. If you want to publish both a library and an application, you have to either version them with ridiculous version numbers, or you have to split the two.