Hacker Newsnew | past | comments | ask | show | jobs | submit | d-cc's commentslogin

Or there is mass neurocompromise.

At least we have a pardon czar now. So many people have been coerced into committing crimes, with said coercion taking many different forms, there needs to be mass pardons across the board.

https://en.wikipedia.org/wiki/Alice_Marie_Johnson everybody check her out.


Great work guys, I'm glad you were able to catch this before it propagated further.


Python's absolutely fine to use for a "serious backend thing" at a telecom firm.

It's a language that attracts casuals, but that does not mean it's incapable of being used for serious software engineering. The only scenarios where I wouldn't use python for a "serious backend thing" are scenarios in which there are dramatic cost/performance/etc consequences resulting from the overhead of using python which would be substantially reduced if using $lowLevelLanguage. Even then, there's always the option of outsourcing specific units of functionality to say, c++, anywhere the performance difference actually matters.

I would say that for the vast majority of use cases, acceptable performance could be easily achieved by simply writing better python.

Writing this reply brought to mind some absolutely atrociously inefficient ORM code I encountered in a python codebase recently. If you don't have an understanding of how to utilize SQL efficiently, it doesn't matter what language you're using to construct the SQL queries, the software engineering equivalent of warcrimes is possible in any language.


Location: Vancouver, WA / Portland, OR Remote: Highly Preferred

Willing to relocate: I'd prefer to stay in OR/WA, but can compromi$e

Technologies: Python(Django|Flask|Fastapi), Javascript/Typescript, CI/CD (circleci|github actions), Testing (pytest|jest|etc), Docker, Nginx, Linux (prefer debian variants [although I allegedly have code in redhat]), ... pretty much everything both code&infra that goes into serious web app/api, while also ensuring best practices are followed.

Résumé/CV: https://liberfy.ai/resume.pdf

Email: ccarterdev@gmail.com

Github: https://github.com/cc-d (getting close to 1 year of green squares)

Shill: https://liberfy.ai also contains a project showcase/status tracker


Location: Vancouver, WA (soon to be probably Seattle WA)

Remote: Highly Preferred

Willing to relocate: I'd prefer to stay in OR/WA

Technologies: Python(Django|Flask|Fastapi), Javascript/Typescript, many others to various extents

Résumé/CV: https://liberfy.ai/resume.pdf

Email: ccarterdev@gmail.com

Github: https://github.com/cc-d (getting close to 1 year of green squares)

https://liberfy.ai also contains a project showcase/status tracker


Location: Portland, OR

Remote: Highly Preferred

Willing to relocate: I'd prefer to stay in OR/WA

Technologies: Python(Django|Flask|Fastapi), Javascript/Typescript, many others to various extents

Résumé/CV: https://liberfy.ai/resume.pdf

Email: ccarterdev@gmail.com

Github: https://github.com/cc-d (those are real commits)

Shill: I'm working on something called open2fa that I want to have launched within a couple more weekends max, I think it's pretty cool. https://open2fa.liberfy.ai/ here's how it works.


>We didn't disqualify anyone for using AI, we disqualified them because of their dishonesty. If you can't trust someone in an interview, how can you trust them in a remote environment?

Radical honesty has been a core cultural component to many a strong team, I'm glad to see somebody else mention this. There seems to be something unique about the relationship between codering and the concepts of transparency, honesty, and truth more broadly.

Or maybe that's just a consequence of version control :)


It’s a fundamental part of (reliable) engineering. Many a person has died historically when in ‘harder’ engineering someone was hiding things, and someone being able to acknowledge their lack of knowledge is key to not getting into that state - or being able to progress/grow at all, IMO.

Chernobyl being one prominent example.

At least in a field like engineering where actual successful results/working output matters, anyway.

There are other fields where the same dynamics are not in play.

One cannot solve (or even avoid) a problem that one refuses to acknowledge exists, after all.


I don't think radical honesty would ever work in a workplace. A very high level, yes, but not radical as it's usually meant.


The relationship of capitalism to truth is very significant as well, or maybe 'value generation' would be a better term to use here than capitalism.

Or as I usually phrase it, 'money is allergic to lies'.

Say you have an organization that is producing a product/service that provides genuine value for its users, and have a team of talented, hardworking people. Any factors related to the operations of said organization, obscuring those factors from the value producers can only lead to less effective operation overall, as the producers have less/lower quality/false information to work with.

"I don't feel like this is workplace appropriate" does not violate the 'radical honesty' principle.

At least internally, anyway. If your objective is to make as much money as possible, you probably don't want marketing to be radically honest LOL


>There seems to be something unique about the relationship between codering and the concepts of transparency, honesty, and truth more broadly.

And what is worse than lies, is self delusion, even if honest. To nit pick on radical honesty, my observation is that most people won't tolerate it, plain honesty appears to be the sweet stop inmost cases.


Now all we need is a PiPy and we'll have all the pies


PiPi would complete the set but that would be (doubly) irrational…


I think you mean transcendental.


That works too. Perhaps that would be how the pie would taste: truly transcendental, but I don't think it could ever be finished.


THANK YOU. This was my first reaction as well.


Location: Tennessee

Remote: only ever worked remotely, since ~2015 (but willing 2 compromise 4 $)

Willing to relocate: if you pay me enough

Resume/CV: https://liberfy.ai/resume.pdf

Email: ccarterdev@gmail.com

https://github.com/cc-d <- I've been practicing intensely for almost 2 years straight now, and it's starting to show. I generally prefer to stay within the python/react web ecosystem, but again, compromi$e


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: