Hacker Newsnew | past | comments | ask | show | jobs | submit | kramer2718's commentslogin

I agree that simply emailing in copies of identity documents after the fact shouldn't be sufficient. However, there should be a verification process that includes verification of identity documents through legal means, including perhaps a processing fee. The fee would preclude many attackers from even trying to break this process.

Maybe this would only work for new accounts as you'd probably need to provide identity information on before losing access.


2015: This meeting could have been an email 2025: This enterprise development project could have been a spreadsheet


Yeah it really amused me that he went through tons of steps, buying lots of new hardware, etc before simply unchecking the delete images box.


You also shouldn't delete from the SD card using your laptop anyway. Always use the in-camera format. This was a bad workflow from the beginning, no idea why you would ever click "Delete after import" when importing directly off an SD card.

Also a good idea to copy to multiple locations when importing. When I do professional work and import into Lightroom from SD card I have it set to create two copies - import to my external SSD (the "working" copy) and also copies the files to my NAS (which is then backed up to the cloud).

Nowhere in that process do I ever delete anything.


This looks AMAZING! Will be doing this for an upcoming project.


Finally! Isaac Newton is pleased.


This is a largely political problem. Cross pollination does not affect the utility of commercial help-only its legality. You can study wind dispersal, etc, but at the end of the day, the problem is a bunch of clueless old men.


I live in a state that 'inadvertently' legalized THC products when trying to pass hemp legislation in 2022, so... yeah. Not that I'm complaining, mind you. It was followed closely by actual legalization because nobody in their right mind was going to try to roll it back and stay in office.


Isn't it also a problem for breeders? I would think pollenation could cause issues for indoor as well as outdoor crops, especially specific strain breeding and understanding pollenation patterns would help mitigate some of that.


It's not a very popular opinion, but I don't think any grower really knows what strain they are growing anyways. I think the strains have been so mixed and matched, and probably some growers will call theirs a specific strain just to sell more of it. And with how long Marijuana growing was underground, the sources of the seeds are totally undocumented. It's basically like a big game of telephone at this point.


AFAIK they mostly grow from clones, and thus, would be completely unaffected by pollination. Unless I misunderstand plants, pollination impacts the seeds produced, and therefore the subsequent generation. So long as it keeps being cut and propagated, rather than grown from seed, you could be relatively certain of near identical genetics.


Clones are good. But it is not possible to keep a clone line going indefinitely.

Periodically you need males and females doing their wonderful thing and mixing it all up from seed


For example, every apple variety out there. Every potato variety out there. Every garlic variety out there. Grape varietals. All gone because their clone lines expired. Not being able to propagate clone lines is why we can't have seedless oranges or watermelon or grapes.


What makes clone lines no longer able to propagate?


> But it is not possible to keep a clone line going indefinitely

What is the mechanism that prevents this?


I am no botanist

But I think the DNA degrades over time

Mēh! What we do not understand about genetics matters more than what we do....

I am no botanist


I think hemp farmers use seed more than clones, which are more popular in the THC supply chain


There is also little evidence that the strain has any effect on the pharmacological effects of cannabis, beyond the amount of THC per gram of flower (potency). Although it can greatly influence the smell/taste, which is meaningful.

However, if you’ve tried the “same” strain from multiple growers you’ve likely found that the smell can vary significantly, and (as a consumer) there’s really no way to know what the flower’s aroma (and appearance) will be without direct observation. This is aligned with your hypothesis.


I never thought about this. It would be interesting to run mass spec on resin samples from different growers to see the interval of genetic variation


And yet Headband really did feel like you were wearing a headband =)


The motor cortex goes across the brain like that.


> This is a largely political problem

Is it? "leading to contaminated seeds, reduced oil yields, and in some cases, mandated crop destruction" sounds not like a political problem, or you mean the causes for those things are political?


These issues at least partially stem from the politics surrounding cannabis. 'Mandated crop destruction' is absolutely a political problem, because it's just driven by seeds cross pollinating into plants that exceed the arbitrary political limit. Oil yields and contaminated seeds are not specified, but might be due to similar arbitrary restrictions, rather than actual issues with the product


Yields are real impacts from cross pollination and has zero to do with politics.

CBD only strains with THC, vice versa. Lower strengths etc. All impact product quality and impact.


The labeling of seeds as "contaminated" is a political issue. Its not like seeds being pressed for oil are not good for that purpose if they are arbitrarily determined to be contaminated. I suspect the reduced oil yields are the result of the destruction requirements not because the plant made less oil.


(laughs in xzibit)


I realize it isn't your target use case, but I'm tempted to move all of my personal stuff stored in Google Drive over to this.


Look at the code coverage. Not just the line percentage, but look at the more complex pieces. Are they covered or not?

Don't refactor it right away. I'll take your word that the code is shit (frequently the case), but you don't know the idiosyncrasies well enough to know what to do with it.

After you've worked with the code a while, you'll be able to attempt a large refactor. Until then, gather low hanging fruit. Clean up confusing variable names. Add comments where needed. Write your new code as clearly and cleanly as possible. Use a tool like sonar to inspect your new code so that you don't introduce new problems.

Most importantly, ADD UNIT TESTS. That will make sure that your new code works with the old and it will allow you to attempt a larger refactor while being sure that you aren't breaking anything.

If necessary, you may need to add some integration tests as well.

I've been in your shoes. Bad code is no fun, but don't let it get you down. Focus on the happy parts of your job (team, culture, whatever). Good luck!


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

Search: