> Due to material changes during construction, the building as initially completed was structurally unsound.
67 karma · joined December 10, 2015
> Due to material changes during construction, the building as initially completed was structurally unsound.
Some other really good content out there is Game Historian, RetroRGB, My Life in Gaming, and Wrestling with Gaming. If you're into hardware restoration then Retro Man Cave has a lot of content too.
I don't know if you'll have better luck switching after making such a large investment in Python, but if you do find something to supplant it please document your experiences for other to learn from.
I would suggest starting by gathering data to show you CEO where you think you can make improvements. Sometimes just applying a standard processes is not enough to convince management of the benefits if they are not yet bought in.
>I’m not sure ageism is really a big problem though.
I'm not sure you can put both those statements together without sounding uninformed.
cat file.txt | grep -v secret | sponge file.txtI can imagine other improvements but all would hurt the site popularity in the short-term. Enough that I doubt SO would ever implement them. This is probably at the core of why the reputation for SO continues to worsen over time.
Hopefully they can turn it around since the core features of the site are invaluable.
BTW, I must be one of the few that actually like the new (non-touchbar) keyboard. The only thing I would change are the arrow keys.
Why does Lenovo (and Dell) make it so difficult to actually buy an X1 without being a product expert? The shop page has 6 or 7 base configurations that all can be customized. To me, this is a really good sign they are not consumer focused, but instead catering to the direct enterprise buyer. Someone who is more willing to spend hours deciphering the subtle difference between every configurations and go through multiple customization flows to find some ideal configuration for a large multi-unit order.
Can someone explain why it's so hard for PC companies to move away from this purchasing model when the simplified Apple flow is generating 10x or more sales directly to consumers.
1) Remind Me Later (https://itunes.apple.com/us/app/remind-me-later/id408236729?...) - Let's you create Google calendar events from your desktop with single shortcut. It works like google "quick event" text box. Just write the reminder with a day or time at the end. I created a new calendar in Google to group all my reminders.
2) Calendar Notifications Plus (https://play.google.com/store/apps/details?id=com.github.qua...) - Ensures you get a notification for every calendar event, even ones without an alarm. From the lock screen you can dismiss or snooze the reminder. You can configure the list of snooze times and the default swipe length. You can move the event to a different date and time. You can pick which calendars it monitors, so if you just want it to see your reminders, it can.
pip-compile --upgrade
pip-compile --upgrade-package
are also necessary features to quickly track your dependencies (and transitive deps).pipenv uses pip-tools, but they haven't exposed these features as far as I can tell.
Slack solves a lot of this. The channels are opt in. If you don't want to follow something, just leave. Email is now just for async messages and is less of a distraction during core hours.
If your team or Co uses one channel for all your discussions, then I suggest that you find a way to split out the primary topics in a way that lets everyone filter the wheat from the chaff.
Like others are saying, don't blame the tools for being misused. Ultimately you have to learn how to efficiently communicate with your team and be disciplined enough to know what tool to use for each type of task.
Someone created a very relevant issue, and I would suggest taking the time needed to close this before doing any more publicity. https://github.com/pypa/pipenv/issues/1398
You can't reasonable say that both methods are equal. Would you still recommend the (if res != exp { t.Fatal(...)}) in this case? If "No", then doesn't that mean you actually prefer more complex assertion primitives?
Do you only use "if" test conditions in C, C++, Java, Python? Why or why not? If "No", why is it acceptable to use more code and logic just because you switched to Go?
Bisect is great to find the commit that caused a bug, because the commit narrows down the code to inspect to fix the bug.
Maybe I'm missing something here, but git bisect doesn't seem to apply in this case.