It may be due to the quality of the clay, or the lack of clay at all, for making the bricks. I saw a documentary on this just a few months ago aired by our local PBS station on this very subject.
When you add salt to bread, and the recipe calls for one teaspoon, a teaspoon of kosher salt is not the same as table salt or sea salt. So how much is it? (It's significantly different.)
When something calls for three cups of flour, and it's a humid day, or a dry day, does that affect the quantity? Yes it does. Significantly enough to affect bread.
Both of the above reasons are why bread bakers weigh all their ingredients, including water.
You can weigh things with either metric or imperial units. Measuring volume when you want to know mass is a mistake you can make regardless of what units you're using.
I don't see how weighing the flour will help. A given volume of moist flour will weigh more than dry flour because of the water in it, so you'd still have a problem on humid days.
Real cooks would never use table salt. Its almost always sea salt or kosher salt. Would you rather have something nature made or something made by a chemical process in a plant?
I own a lot of Grilling/BBQ books and normal recipe books, almost everyone says to never use table salt somewhere in the book.
My Himalayan salt is quite good for seasoning and was deposited millions of years ago. Compare that to Morton's table salt with iodine my grandmother used to use.
Iodized salt is responsible for raising the average IQ of billions of people around the world because iodine deficiency leads to intellectual and developmental disabilities. It's not some sinister additive that people need to avoid. It's one of the most successful public health efforts ever.
I'm sure I would get the recommended Iodine dose from any sort of processed foods I eat or from any cheaper restaurants I frequent that use table salt.
There are many people that dont cook at home and I doubt their Iodine levels are low.
Also I never said it was some sinister corporation spreading false info.
They are very different - table salt conforms to a quality standard while the others have varying trace contaminants. They may add to flavor, but not in any reliable predictable way. And the major active ingredient of both is sodium.
Its fun to play with cool, colorful salts. By the time the cooking is done, I'd bet cash money no one can tell the difference.
By the time the cooking is done, I'd bet cash money no one can tell the difference.
I suspect you'd lose that bet - informally I've tried many experiments with iodized and non-iodized salts, and the iodine can change flavor.
Besides that, one of the main reasons to use different salts is crystal size which can have significant effect (depends on what you are doing, obviously). For example, koshering salt is called that because of its use in koshering meats, where the large crystal structure helps control absorption. Likewise in "finishing" applications.
If you follow many recipes are use table salt instead of kosher salt I guarantee it will come out salty.
Serious Eats has an article and it really validates a part of both of our points[1]:
>"So long as your salt is going to be dissolved and distributed evenly into the final dish...there's no reason to use kosher salt...Just remember, check your recipes and make sure to compensate for table salt's density when adding it."
If you have access to Good Eats, Alton Brown explains it pretty well.[2]
Real cooks use table salt all the time. Other salts are mostly useful as finishing salts (where the subtle distinctions in flavor and texture between different salts, or different sized grinds of the same salt, come out, and where color distinctions can impact presentation) rather than in cooking itself (where they don't.)
> My Himalayan salt is quite good for seasoning and was deposited millions of years ago. Compare that to Morton's table salt with iodine my grandmother used to use.
...and, what? Both are good for seasoning, the table salt with iodine is better for avoiding the (otherwise fairly common) iodine deficiency (conversely, its a good thing to avoid if you are iodine sensitive). I'd rather use the Himalayan salt as a finishing salt for some things.
Also, table salt vs. other salt and iodized salt vs. non-iodized salt are orthogonal distinctions (and table vs. other salt is a different distinction than "made in nature" vs. "made in a chemical process in a plant".)
Kosher, Sea, and some other salts are available iodized, and table salt is available non-iodized.
It's awful. I thought HN just didn't care. Why is this so hard? I do this every day for work and HN should be dead simple. Is this saying HN doesn't have anyone who knows how to do this?
EDIT: My initial post was from my phone. Now I'm on my workstation and I see the markup here is antiquated, pre-1998 HTML. No wonder this is so horrid. You should be ashamed but, still, I could do better.
Using the words, 'cowardly' to describe other people you don't know, and saying 'I'm better than you', to people you don't know, and saying 'my grandmother could write better markup', to a group of people you don't know, probably just made them classify you as a 'troll'.
I saw the markup, and saw they needed guidance (https://news.ycombinator.com/item?id=10489954), you saw the markup and decided they weren't worth helping. That's sad really. No one is an expert in everything.
"In order to reach collaborative nirvana, you first need to learn and embrace what we call the “three pillars” of social skills. These three principles aren’t just about greasing the wheels of relationships; they’re the foundation on which all healthy interaction and collaboration are based.
Humility
You are not the center of the universe. You’re neither omniscient nor infallible. You’re open to self-improvement.
Respect
You genuinely care about others you work with. You treat them as human beings, and appreciate their abilities and accomplishments.
Trust
You believe others are competent and will do the right thing, and you’re OK with letting them drive when appropriate."
I dunno that that's a fair criticism... by that same argument you could say yacc/bison is for people who don't know how to use C to write a parser. This looks like an attempt to do something along the lines of Parsec from Haskell, but in C.
Edit, because it looks like we hit the max reply depth: It's not like this is ever going to seriously replace Bison, I think it's just someone trying a different approach. It's not like flex/yacc/bison are the absolutely most perfect lexer/parser that can possibly exist. If people didn't try and reinvent the wheel every now and then, we'd still have stone wheels.
But doing this in C already exists and works well. I don't understand the point of it. Although, in this day and age, rather than use the standard Unix toolset, people invent their own tools as if they are new. "Make" versus "npm" for example.
Recursive descent parsing can handle different class of languages from what yacc or bison can do. It is possible to build lexerless parsers this way (so scrap your old useless flex).
I seriously doubt it ever will, but you have to start somewhere.
I've used Parsec before and it is certainly nice. Honestly I think it's a bit weird to try and shoehorn it into C, but hey maybe something interesting will come out of it.
What bugs me is the suggestion that just because bison works well enough, nobody should try and make a new parser generator in C. They will probably not take over the wold, bison is big and battle tested after all, but bison is itself also a replacement for older tools. And hey, maybe mpc here will succeed and revolutionize parsing for the best; then we can have this discussion again in 20 years about someone attempting to replace it.
What you just said is this new thing isn't as good, and probably never will be, but you imply we should use it, even though the current tools are better.
See my complaint? If they are going to introduce a new tool, it must be better than the current tool. It's not and it's worse and not as mature.
I didn't say you should use it, nor would I. Only that it isn't pointless/futile to attempt. No tool will be as mature as bison or what have you until it has also been battle tested for 25+ years, but 25 years ago bison was also new and upcoming.
Not to mention that this is not even really a parser generator like bison or yacc... it's a combinator library. It's an entirely different way to write a parser. It's like me saying Python shouldn't exist because I know how to write C.
In yacc the generator will tell you about shift reduce conflicts. Once you have debugged the grammar the parser is likely to work. With parser combinators you have no such assurance - you don't know if your grammar has loops, the parser might get stuck easily while parsing. However for a simple and regular input language like sexpr everything is fine.
you can have left recursion, or implicit left recursion in your recursive descent grammar, if you have then the parser gets stuck while parsing a clause that contains left recursion.
Firstly, this have nothing to do with shift/reduce. Secondly, you can safely handle left-recursive grammars in Packrat (which, in turn, can be implemented with combinators).
I see, yes, you mentioned loops earlier. Anyway, it is not a problem for combinator-based parsing, just use Packrat with a left-recursive extension [1]
As a business owner, sometimes it can't be helped, and sometimes you have to think that way cause firing someone is never a pleasant task.
Sometimes you know it must be done but you know the person is nice enough but just not competent, or can't do the job, or the job has changed and they're getting fired for no fault of their own.
There are those times when you fire someone but you feel guilty that, as their manager, maybe you could have done better with them but you didn't have time, were too distracted, too tired.
In companies that get big enough, the percentage of people getting fired for cause gets higher. Then firing people becomes part of a routine. If you let your feelings get involved, it will drive you crazy, so you try not to let that happen.
Wow what a wonderful answer. This is the most clear and succinct way of explaining the transition in dealing with employee termination from a small to larger company.
Regarding the guilt, I think you're right -- a lot of people don't realize that every day spent trying to work with an unproductive employee/coworker is a day lost by the productive one. At a certain point or company-size you can't continue doing it.
I look at this and it reminds of drawings from the late 1800s of people doing things with mechanical devices that we now use electronics for. It just seems very contrived and impractical.
He "blew up," yelling and cursing at Rasmussen. He remembers saying to Rasmussen, "I'm going to PDR [public disclosure request] the shit out of you."
And you want to say the PD could have handled that better? Go into your boss right now and do the same thing. Let us know how he handled that from the unemployment line.
That said - I work for a private firm, not even remotely as crucial as the police dept. cops are trained to deal with all kinds of situations/personalities (my boss is not). The captain could've banned him for a month, instead of permanently. After both of them have cooled down, he could've sat him down and explained that shouting isn't going to help. He could've given him warnings etc. Instead, he seems to have gone on a power trip. Clemans is not some destructive guy, or some criminal. He is just a frustrated over enthusiastic young man. The real losers in this are the people of Seattle.
I hope some other police dept hires him and also he learns to control himself better.
In a government agency that has sensitive information about ongoing investigations about criminal activity and personal information, you can't put up a web page for ANYTHING without approval.
Also, he admits that when that happened, he "blew up," yelling and cursing at Rasmussen. He remembers saying to Rasmussen, "I'm going to PDR [public disclosure request] the shit out of you."
That alone will get you escorted out of a LOT of companies who will say you definitely "did something wrong".
http://ninenet.org/archives/pressroom/st-louis-brick-buildin...
https://vimeo.com/ondemand/brick