Great potatoes... This is not very good advice. Ok for prototypes that are intended to be discarded shortly after writing. Nothing more.
UFODivebomb
joined 1 year ago
How often does a cop look at those and decide not to pull them over because of the trouble?
The bill actually needs to get to his desk first...
We've selectively sampled like 5 metrics and carefully confused population averages with the median and can confidently say: yachts are more affordable. QED you're wrong.
/s
We've created an economy where that is not sustainable.
This fact is bad imo, but it's where we are.
Right in hand with tying healthcare to a job. Can't work? Well then, die.
Weakens our great nation. Makes us less resilient as a whole. Horrible for smaller companies. Which is why the GOP loves these policies.
Beer.
-
Liquid
-
Calories
-
Uh...
They are set in the same universe... Thousands of years apart
Thank you for your service
You all are very offended by the fact that Biden is not the president of Israel. Gonna have to accept at least that fact if real progress is to be made.
"The US president can influence Israel" probably true. But confusing that with "Biden controls Israel" makes ya look dumb.
In not one of these comments did i see anybody proposing direct action like donating to standing together ( https://www.standing-together.org/donatehere )
Or boycott Israel: https://bdsmovement.net/
Nah. Why do that when blaming Biden is better for driving division.
False: Israel is not the 51st state 🙃
Look, this easily falsifiable hyperbole feels nice. I get that. However, the statements are idiotic and make you look idiotic. They do not help and are likely counterproductive.
My advice comes from being a developer, and tech lead, who has brought a lot of code from scientists to production.
The best path for a company is often: do not use the code the scientist wrote and instead have a different team rewrite the system for production. I've seen plenty of projects fail, hard, because some scientist thought their research code is production level. There is a large gap between research code and production. Anybody who claims otherwise is naive.
This is entirely fine! Even better than attempting to build production quality code from the start. Really! Research is solving a decision problem. That answer is important; less so the code.
However, science is science. Being able to reproduce the results the research produced is essential. So there is the standard requirement of documenting the procedure used (which includes the code!) sufficiently to be reproduced. The best part is the reproduction not only confirms the science but produces a production system at the same time! Awws yea. Science!
I've seen several projects fail when scientists attempt to be production developers without proper training and skills. This is bad for the team, product, and company.
(Tho typically those "scientists" fail to at building reproducible systems. So are they actually scientists? I've encountered plenty of phds in name only. )
So, what are your goals? To build production systems? Then those skills will have to be learned. That likely includes OO. Version control. Structural and behavioral patterns.
Not necessary to learn if that isn't your goal! Just keep in mind that if a resilient production system is the goal, well, research code is like the first pancake in a batch. Verify, taste, but don't serve it to customers.