1,365 karma · joined April 19, 2010
I am looking on transferring:
* Google maps location history (have it there since 2009). * Google photos of all the family accounts + plus partner sharing. * Google drive * Gmail * Google extra storage (that I pay already for).
As far as I know, there are no way to migrate cleanly the data. Only crappy ways if possible at all.
Rails took a need: creating a blog engine; and make everything needed to have the simplest and most understandable way of doing it. Going through that example was like: -"Ahh makes sense.". Features were secondary and the focus was on the solution. It was about solving one specific use case and grow from there.
So far, any framework I saw that claims to be the new rails, is speaking about features and the million things you can do.
It feels like Rails was done by a product guy, and all alternatives were done by engineers.
From reading the article, remix feels like the best way to deploy to edge. An engineering problem. Not a user one.
Right now the attendees receive 1 question in the email and two more in the website. This list of questions is fixed for this iteration and should cover 80% of the cases we researched.
We though of allowing the user to customize their questions as a pay functionality so we can adapt better to their flow. Does that make sense?
Hi. We are participating in an accelerator and as part of a hackathon, we just release Rate My Meeting and we are quite excited.
After playing looking for ideas we saw that we all share experiences related to inefficiencies in meetings. We asked ourselves if we want to improve meetings, how could look like the fastest user experience to collect feedback?
Basically, you invite to rate@mymeeting.app and we will ask the attendees for feedback once the meeting is over. One hour after, we will send you the results by email. We also send you a QR code in case you want to display it in one slide.
Check your spam, play with private events, and expect some bugs. After all, it was one weekend.
We don't know if we pursue the idea, but... what do you think?
Thanks :)
And if I need to have other kind of client... like a nas to do that... Why I need the cloud?
It's alignment with the company structure is.
The same way Conway's law tells us that company structure and the communications should be in sync, the architecture should match the teams.
As a rule of thumb... the good architecture is the one that minimize the communication within the different teams.
Your IP: 91.64.84.221 Error code: 16 > This request was blocked by the security rules
It might be requests from outside the United States.
Anyway: * The cache from google: http://webcache.googleusercontent.com/search?q=cache%3Ahttp%...
* Arhive.org https://web.archive.org/web/20210215030515/http://www.ercot....
If the domain knowledge is on the code, you can only refactor. If the domain knowledge is on the team, then rewrite tends to be faster.
Most rewrites fails because the team rewriting is not the team that did the initial development.
The go language spec is one of my favorite things about go. Is a learnxiny on steroids. In less than an hour, you fully understand the language.
I am curious to see how this functionality will change the spec. Will it double it in size?
1. <Enter> Press Enter.
2. ~ Press Tilde.
3. . Press dot.
This disconnects from the remote host.
If you want more: `man ssh` and look for "ESCAPE CHARACTERS"
I think is mandatory if you really want to understand how Linux base os works.
How, depends on different factors. Without trust on the company, their manager and their peers and employee will be likely to quit.
Over the years, I observe trust being in direct correlation with 5 kpis:
* How often the word "politics" is being used in a daily base.
* Miss delivery (delivery something that don't fulfill the goal, in features or time).
* Miscommunication/misunderstanding. (The need of repeating the same message more than once).
* How often the word meeting is being used negatively.
* Times conflict was avoided.
Improving this kpis, by techniques mentioned in other comments, in my experience, will improve trust and employee retention.
Or as you said, the domain knowledge has changed from the original.
If knowledge is on the team because the company is stable, rewrite. 37 signals is a clear example of this.
If the knowledge is in the code, because multiple people or teams worked on the code base over the past few years, refactor. A rewrite will be the recipe for disaster.
I never found an exception to this rule.
In my experience, the problem is different. Company X does not want to translate into different languages, different markets. For example: Apple, Microsoft, Samsung. Amazon video. If you want to see German available products or prices, it have to be in German.
My curve of interest gets reduce over a day. After one week of not working, it is restore.
Curious if this works out to someone else.
Most venture startups are focusing only on the first part. Slow-Growth focus ones on the second.
Once you get used to one model, is hard to switch to another.
For what I remember, the lead free had a higher melting temperature. At least back in the days.
Took one week to get used to.
I remember the change, where I was not able to buy the old one. I remember that it had a slightly higher melt temperature.
Can you buy it in America?