189 karma · joined February 19, 2017
I suppose that's true! Practically speaking, it would be nice to have one testing framework to learn and use over-and-over again, but that's also kinda counter to what I'm used to in the JS world.
One question I have about Rome is why it tries to take on the testing framework too. I really like the idea of it having all the build tooling together, but testing seems like a sort of separate thing. Other environments I've used let libraries fill the gaps for testing, including JS. Is there a big advantage to pulling it into Rome?
I too am a big fan of oatmeal. Funny enough, I like it a bit different than the author does. Particularly, I enjoy it with a less runny/liquid texture, and I don't submerge it like the author does afterward either. My setup I've eaten year round for 5 years now is:
* 1 cup dried old-fashioned oats
* Water plus a dash of creamer (oat milk recently) to submerge the oats
* 1-2 tablespoons of peanut butter
* Cinnamon to taste
* Sometimes flax seed to taste
The biggest thing is the cooking. On the stove top, bring the liquid boiling _and then_ add the oats. Don't add the oats before hand, as that changes their texture a bit too. Then I'll turn it down to maybe medium-low temp and cook most of the liquid off. It's usually 5-10 minutes. In the microwave, I mix the liquids and oats together because what other choice do you have? Then it runs for 3 minutes on high.
You'll end up with a bit of a softer texture, but the peanut butter thickens it up to be much more hearty. It's hard for me to enjoy other oatmeal that's runny.
It takes some effort, but it's fairly straightforward if you can find ways to substitute it into your daily meals. I like taking an existing meal and just replacing the animal products from it. One example I like is a chicken curry wrap. It's just chicken mixed with mayo, curry powder, celery and onions, all stuffed into a wrap. I've substituted a lightly fried tofu in place of the chicken and a vegan mayo instead.
I would've appreciated the article more if they skipped mention of "Rich Dad, Poor Dad" entirely.
I'm definitely an amateur when it comes to networking stuff. At the time, the _only_ issue I had was with all of my Digital Ocean droplets. It was confusing because I was able to get to them through my LTE connection and not able to through my home ISP. I opened a ticket with DO worried that it was my ISP blocking IP addresses suddenly. It turned out to be this outage, but it was very specific. Traceroute gave some clues, but again I'm amateur and I couldn't tell what was happening after a certain point.
So yeah, I too would love a really easy to use page that could show outages like this. It would be really great to be able to specify vendors used to really piece the puzzle together.
While I'd definitely encourage looking at a hybrid, it may be worth the while to wait a few more years and see how full-blown electric cars hold up. That's my plan at least.
Another huge factor has changed my thinking on dependencies too. My employer has legal and security requirements around all dependencies. Anytime a new dependency is considered, it has to have the license reviewed which takes time, and known CVE's have to be addressed (patched or mitigated otherwise). I consider these good since it helps in the sense that the costs of dependencies forward, but certainly a pain.
So I guess my perspective change is simply one of trying to understand the trade-offs. Some are well worth the cost because they're cheap, you won't get much benefit of your own, and will get benefit from a common one for everyone developing in it (testing libraries are one example). If a UI library is applicable to your project, of course a modern common one is a good choice, though you will pay for a lot of dependencies. Then there are other options which are more context-sensitive. Examples that come to mind are date/time libs, math libs, collection helper libs, etc. Sometimes they make sense to have, but oftentimes today can be substituted for a simpler function, though this can change with time too.
This really just turned into a ramble. So I guess I'll conclude with this: if you're getting started and learning, maybe try and skip libraries until you really feel the pain and then introduce one when you need it. It may help to build up piece-by-piece and reduce the anxiety you feel about it.
If the app maintains a session, then that depends on how long the app allows sessions/tokens to live for at that point. The Yubikey won't come into play until login is required again. So, I think you're getting at a different part of the security model at that point.
I wish this was my experience with security teams. The teams I've worked with through the years are generally disconnected from any product teams and support a wide-ranging enterprise. So they simply don't have the resources or specific technical or product knowledge to do it. It would be awesome to have a security person on the team directly mitigate issues, understanding the product, and making everyone else more security knowledgeable. I've just never seen it happen though. But I digress.
I agree. These new sets of headers look useful and simple to get going, and even would be useful to deploy today. So it seems worth checking out!
If that's the case, that leads me to wonder if your body wants you to adjust throughout the year. Like when the sun comes up earlier, should the feast change from 6am to 1-3pm instead? Or does that adjustment not really matter?
It's nice to have things that run well with relatively small changes.
This is definitely one of the clumsier parts of GnuCash. Still works though.
This was a big realization for me. I tend to prefer getting the "robots" to do things for us (in other words, automate things). Developing an intuition of what's happening with your money is hard when you use an automated tool though.
The process of managing the ledger bi-weekly really adds something more for me. Working on each entry to determine a category, writing down amounts, noticing how many entries I've entered into a category each session, and looking at it in aggregate afterward gives me some greater sense of how my financial life works. I can almost picture writing the transactions in GnuCash before I even do it.
I get what you mean about it being complicated though. I learned the bits I needed to get by and mostly stick to that. So that works for me. In the long run, the double-ledger manual style is what I think is most important.
1. USB devices. If you need to move software from outside the air gap to inside, it's pretty easy to imagine somebody copying malicious software unintentionally through that. You might think that typical AV could detect it, but that could either be worked around, disabled by the operators of those systems, or simply not up-to-date because they're in the air gap.
2. Sometimes, air-gapped systems still have some kind of tunnel that allows an exceptional connection between a system outside the air gap. If you knew how to access that tunnel, you could effectively compromise the air gapped network.
I'm sure there are more ways too. But those are a few I know off-hand.
I think the team members themselves should be fine. In normal conditions, they should mostly be able to function and keep moving forward without strict and constant guidance. And we're all feeling some degree of pressure right now. So at least team mates should get that leeway will be needed.
A few points:
* Be sure to be clear with the team. It's reasonable to need some leeway, but just state it clearly. You may even get volunteers to handle some of your typical technical responsibilities. Good for them, good for you!
* Give other team mates leeway too. Odds are they are in similar situations. So if somebody seems behind or there are just more issues than normal, don't assume bad intent. It's probably similar to your situation.
There are plenty of scenarios where it wouldn't fit (references, specifications, etc) of course. So I don't think it's great everywhere. But yeah, overall I find it easier to read when starting out on a big topic.
The substance behind some of the questions could be useful IMO. One would need some rapport and context to use them. If they were reworded and delivered in ways that made more sense for those people, it could be helpful.
* I found an interesting music instance which had some cool music videos. Well worth the while. Though now I can't find it while on another computer. * I tried to find an instance with some kind of software dev/programming videos. Haven't been able to find anything really yet.
That's about as far as I've got yet. Maybe there's room to improve search/discovery. Or maybe I just need help being pointed to the right spot.
A lot of this is off-the-cuff, and not match up with what you're aiming for here. Hopefully some of it is useful though.
1. During the process, I couldn't quite figure out how I was doing or what I was doing wrong. One example was the determining if a number is a palindrome or not. I didn't see indication about if I was failing certain tests in the test suite, or if I had an issue with syntax, etc. Some more feedback would help here.
2. A minor thing, but on my laptop I noticed that while the line would wrap, the code itself is running under the chat portion of the room. Makes it harder to edit.
3. I think the room concept is nice, especially if I just want to jump into a certain class of problems and go. However, it would be cool if you could have one room indefinitely. Perhaps a private room of sorts?
4a. It would be nice if you could request the difficulty of problem in the room itself. Right now you need to make a new room to match the difficulty, but I think that having problems come to that room might be nice.
4b. In addition to requesting difficulty of problems, requesting kinds of problems might be nice too. I can imagine a CS student being in some kind of data structures/algorithms class and wanting to focus on that specifically. Something like "medium difficulty problems involving trees" or "hard problems involving strings."
Anyway, cool project and good work!
In addition, https://binarysearch.io/api/rooms just returned a 502 Bad Gateway. Maybe the site is getting hugged by HN.
Maybe the original paper discusses the point though? Perhaps they have a way to normalize temperatures to a baseline across all data sets and evaluate that way.
> As part of the study, the authors investigated the possibility that the decrease could simply reflect improvements in thermometer technology; thermometers used today are far more accurate than those used two centuries ago. “In the 19thcentury, thermometry was just beginning,” Parsonnet said.
> To assess whether temperatures truly decreased, the researchers checked for body temperature trends within each dataset; for each historical group, they expected that measurements would be taken with similar thermometers. Within the veterans dataset, they observed a similar decrease for each decade, consistent with observations made using the combined data.