[Programming] Initial commit
Infidel
HereticRegistered User regular
HereticRegistered User regular
LICENSE wrote:Creative Commons Legal Code
CC0 1.0 Universal
CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN
ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS
PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM
THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED
HEREUNDER.
Statement of Purpose
The laws of most jurisdictions throughout the world automatically confer
exclusive Copyright and Related Rights (defined below) upon the creator
and subsequent owner(s) (each and all, an "owner") of an original work of
authorship and/or a database (each, a "Work").
Certain owners wish to permanently relinquish those rights to a Work for
the purpose of contributing to a commons of creative, cultural and
scientific works ("Commons") that the public can reliably and without fear
of later claims of infringement build upon, modify, incorporate in other
works, reuse and redistribute as freely as possible in any form whatsoever
and for any purposes, including without limitation commercial purposes.
These owners may contribute to the Commons to promote the ideal of a free
culture and the further production of creative, cultural and scientific
works, or to gain reputation or greater distribution for their Work in
part through the use and efforts of others.
For these and/or other purposes and motivations, and without any
expectation of additional consideration or compensation, the person
associating CC0 with a Work (the "Affirmer"), to the extent that he or she
is an owner of Copyright and Related Rights in the Work, voluntarily
elects to apply CC0 to the Work and publicly distribute the Work under its
terms, with knowledge of his or her Copyright and Related Rights in the
Work and the meaning and intended legal effect of CC0 on those rights.
1. Copyright and Related Rights. A Work made available under CC0 may be
protected by copyright and related or neighboring rights ("Copyright and
Related Rights"). Copyright and Related Rights include, but are not
limited to, the following:
i. the right to reproduce, adapt, distribute, perform, display,
communicate, and translate a Work;
ii. moral rights retained by the original author(s) and/or performer(s);
iii. publicity and privacy rights pertaining to a person's image or
likeness depicted in a Work;
iv. rights protecting against unfair competition in regards to a Work,
subject to the limitations in paragraph 4(a), below;
v. rights protecting the extraction, dissemination, use and reuse of data
in a Work;
vi. database rights (such as those arising under Directive 96/9/EC of the
European Parliament and of the Council of 11 March 1996 on the legal
protection of databases, and under any national implementation
thereof, including any amended or successor version of such
directive); and
vii. other similar, equivalent or corresponding rights throughout the
world based on applicable law or treaty, and any national
implementations thereof.
2. Waiver. To the greatest extent permitted by, but not in contravention
of, applicable law, Affirmer hereby overtly, fully, permanently,
irrevocably and unconditionally waives, abandons, and surrenders all of
Affirmer's Copyright and Related Rights and associated claims and causes
of action, whether now known or unknown (including existing as well as
future claims and causes of action), in the Work (i) in all territories
worldwide, (ii) for the maximum duration provided by applicable law or
treaty (including future time extensions), (iii) in any current or future
medium and for any number of copies, and (iv) for any purpose whatsoever,
including without limitation commercial, advertising or promotional
purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each
member of the public at large and to the detriment of Affirmer's heirs and
successors, fully intending that such Waiver shall not be subject to
revocation, rescission, cancellation, termination, or any other legal or
equitable action to disrupt the quiet enjoyment of the Work by the public
as contemplated by Affirmer's express Statement of Purpose.
3. Public License Fallback. Should any part of the Waiver for any reason
be judged legally invalid or ineffective under applicable law, then the
Waiver shall be preserved to the maximum extent permitted taking into
account Affirmer's express Statement of Purpose. In addition, to the
extent the Waiver is so judged Affirmer hereby grants to each affected
person a royalty-free, non transferable, non sublicensable, non exclusive,
irrevocable and unconditional license to exercise Affirmer's Copyright and
Related Rights in the Work (i) in all territories worldwide, (ii) for the
maximum duration provided by applicable law or treaty (including future
time extensions), (iii) in any current or future medium and for any number
of copies, and (iv) for any purpose whatsoever, including without
limitation commercial, advertising or promotional purposes (the
"License"). The License shall be deemed effective as of the date CC0 was
applied by Affirmer to the Work. Should any part of the License for any
reason be judged legally invalid or ineffective under applicable law, such
partial invalidity or ineffectiveness shall not invalidate the remainder
of the License, and in such case Affirmer hereby affirms that he or she
will not (i) exercise any of his or her remaining Copyright and Related
Rights in the Work or (ii) assert any associated claims and causes of
action with respect to the Work, in either case contrary to Affirmer's
express Statement of Purpose.
4. Limitations and Disclaimers.
a. No trademark or patent rights held by Affirmer are waived, abandoned,
surrendered, licensed or otherwise affected by this document.
b. Affirmer offers the Work as-is and makes no representations or
warranties of any kind concerning the Work, express, implied,
statutory or otherwise, including without limitation warranties of
title, merchantability, fitness for a particular purpose, non
infringement, or the absence of latent or other defects, accuracy, or
the present or absence of errors, whether or not discoverable, all to
the greatest extent permissible under applicable law.
c. Affirmer disclaims responsibility for clearing rights of other persons
that may apply to the Work or any use thereof, including without
limitation any person's Copyright and Related Rights in the Work.
Further, Affirmer disclaims responsibility for obtaining any necessary
consents, permissions or other rights required for any use of the
Work.
d. Affirmer understands and acknowledges that Creative Commons is not a
party to this document and has no duty or obligation with respect to
this CC0 or use of the Work.
0
Posts
Supposedly within the 250k limit, but there has been zero communication so far.
Small but common misunderstanding here: 250k isn't a limit but the guaranteed minimum that the FDIC will recover for a depositor. The FDIC will do their best to recover all your money. From my understanding.
Which is all fine as an individual, except these are businesses which will have accounts well in excess of the minimum. And getting your hands on money beyond the minimum may take some time to sort out. IIRC 97% of SVB's accounts are above the 250K minimum. Given they are apparently the VC bank there's a lot of assholes puckered right now.
Everybody, let's thank Peter Thiel for engineering a run on the bank! Not clear what would have happened if he hadn't done it since their long term portfolio was problematic, but certainly his "GTFO now" order to VC's under his direction was an immediate cause of the bank run.
Fizz Buzz in Tensorflow:
https://joelgrus.com/2016/05/23/fizz-buzz-in-tensorflow/
FDIC said all deposits are available to retrieve today in full somehow, no idea what bucket they're getting that money from though.
"After receiving a recommendation from the boards of the FDIC and the Federal Reserve, and consulting with the President, Secretary Yellen approved actions enabling the FDIC to complete its resolution of Silicon Valley Bank, Santa Clara, California, in a manner that fully protects all depositors. Depositors will have access to all of their money starting Monday, March 13. No losses associated with the resolution of Silicon Valley Bank will be borne by the taxpayer."
This was stated yesterday. If anyone can't get their company's billion dollars out or whatever I'm sure we'll hear about it today.
When you stop being able to make payroll that goes south real quick.
Know some companies have been having internal talks and from what I've seen it's all been "okay here's the update, we're okay..."
They do not, in any way, fuck around.
Like this guy was like "I don't understand why this bit of code isn't running" and so we took a look at it. And it looks like it was iterating over the string that he passed in. Now this is 100% the fault of javascript even allowing you to do this dumb shit but whatever he didn't want to take the time to convert the project to typescript. So I ask him what he's passing into the function, and it was a string. So I told him to look at the function and see what the parameters are... And he scrolled to the function and it was taking the parameter (named values) and iterating over it with a forEach. So it was expecting an array and he passed in a string. And I wanted it to be a teaching moment so I asked him what he would do to fix it. I had to stop him like 3 minutes later because he was down and dirty in the weeds talking about rewriting the function to do a thing if a string was passed in...
Basic troubleshooting steps. It didn't finish the work he was working on but it got to the point where he was pulling the data correctly after I helped him fix that one call. Then something else broke and then he looked at me like a sad puppy trying to figure out what was going on. I basically told him he's going to need to drop some console logs and walk through the code and see if the logic he presented is actually being executed the way he expects and to ping me if he gets stuck again.
Also, console.log? What is this, 2011?
So much for the paperless office!
The problem is as follows: sometimes, just out of no where, the debugger will get an "unexpected fault" just stepping over standard code (and it's not a nil/null pointer problem) or when attempting to step INTO a function, it acts like you said "continue to next break point", completely skipping stepping into the function. It doesn't always happen, but it does happen on the exact same lines of code every time, no matter the project. I tried a mixture of upgrading/downgrading versions of GoLand, delve, Go, and dependencies, nothing worked (even going back in time to nearly a year ago on some code when it definitely worked). I tried upgrading from Ubuntu 20.04 to 22.04, didn't work. I then created, from scratch, a Debian 11 virtual machine, installed the bare minimum to get the code and debugger to run, and I ran into the exact same problem. Here's the thing, the debugger works perfectly fine on macOS on the exact same code bases. Hence, my theory is some random library/dependency in Ubuntu/Debian got updated that was some kind of indirect dependency for delve, and now debugging these particular projects just don't work properly anymore, for whatever reason. Here's an even more interesting oddity. So I explained that there are lines of code that always break if you try to perform a step over or step into. However, if you set a breakpoint on the line AFTER the offending line, the program is able to execute the offending line no problem. No faults, nothing. WHAT THE HECK.
Hmm, so possibly an issue with VirtualBox and macOS? Didn't think of that.
It seems like everyone on this team is proficient (or so they say) on other languages. Which I get. But like basic troubleshooting steps are universal.
Out of all the places I've seen and teams I've witnessed, I'd say 1:2 is about the ideal to shoot for.
You can juggle a couple people for mentorship (and triple up on topics!) effectively but beyond that you're making it real difficult, and trying to limit yourself to 1:1 direct mentorship just undercuts your ability to scale up a team and productivity. Empowered and enabled non-seniors get a lot of shit done, especially cause the seniors juggle a bunch of other stuff like meetings and non-coding and mentorship itself.
And in fairness, "a string is an array of characters" is, while logical and technically correct, also not what you intuitively expect out of the damn thing. Swift has native .publisher operators to publish basic types, and guess what String.publisher does? (Hint: It's not publish the damn string as a string.
Yeah I'm pretty consistently getting into huddle sessions with all the devs to help them connect to a docker instance that's running a mysql database. And walking them through how to see the data from DBeaver or whatever SQL tool they're using. There is another senior guy on this team but he's being pulled into other sides of the project so I'm kind of out here trying to keep this ship running correctly without sounding like a fascist dictator on how a PR should look lol.
But it's like my mornings are all meetings with sprint retros and whatnot. Then lunch happens and then post lunch I get an hour or so of dev in and then the messages start flowing in with support requests. I'm not one to leave them to the wolves so I'll gladly help out. But my tickets barely move some days and I hate feeling like I'm not pulling MY weight even though I kind of am.
e: He's clearly more of an architect though. He got the IAC done in no time at all and it seems to do it's business. But this is basic development stuff and he's struggling with it.
He's not reading the documentation? I would imagine that's one of the first basic examples.
Sad part is that I gave him the code that I used on another project. All functions written with documentation lol
Interesting how all the big companies are now going to a long rolling layoff to really twist the knife. They're clearly trying to get some good attrition going.
This is from their AWS/cloud and twitch this time.
Definitely does not spark joy for folks who are about to job hunt.
https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/
ive been googling around how to migrate letsencrypt certs and finding very little and usually that means my mental model of the problem is wrong and i can just leave my old cert behind and make a new one
Otherwise you would have to tolerate some downtime as your server isn't sending certs yet and the domain is HTTP/HTTPS agnostic.
When writing a rest API... If I have something like this:
/customer/{id}/rewards
When you get the rewards data (in an array) does it make sense to include the customer id in there as well?
{ [ rewardId: 1, amount: 10, customerId: 555 ] }To me the id doesn't fit because it's a rewards data element and not customer.