Jump to content
43oh

zeke

Members
  • Content Count

    1,782
  • Joined

  • Last visited

  • Days Won

    102

Reputation Activity

  1. Like
    zeke reacted to dubnet in What is "our" time worth ?   
    Depends on the friend...
     
    Joking aside I would probably take a best guess at the work/learning ratio and try and charge accordingly. If the work was two hours and the learning was 8, charge for 2 hours. If the work or learning took longer no change in the charge but if the work takes only an hour refund an hour.  My .02
  2. Like
    zeke got a reaction from greeeg in What is "our" time worth ?   
    It think it's good to practice The Engineering Craft even when it's only for myself.
     
    Sometimes, it's the compulsion to create something beautiful that motivates me. Othertimes, it's personal pleasure. In the case of my Marquee Clock project, I am working on that clock for the pleasure of seeing my daughter's reaction to it. She's my client.
     
    Personal projects are like workouts. They give me a reason to exercise my skills so that I can see how effective I am right now.  I can then explore, experiment and improve how I implement various solutions.
     
    Ultimately, practice makes perfect.
  3. Like
    zeke got a reaction from tripwire in What is "our" time worth ?   
    It think it's good to practice The Engineering Craft even when it's only for myself.
     
    Sometimes, it's the compulsion to create something beautiful that motivates me. Othertimes, it's personal pleasure. In the case of my Marquee Clock project, I am working on that clock for the pleasure of seeing my daughter's reaction to it. She's my client.
     
    Personal projects are like workouts. They give me a reason to exercise my skills so that I can see how effective I am right now.  I can then explore, experiment and improve how I implement various solutions.
     
    Ultimately, practice makes perfect.
  4. Like
    zeke got a reaction from yyrkoon in What is "our" time worth ?   
    It think it's good to practice The Engineering Craft even when it's only for myself.
     
    Sometimes, it's the compulsion to create something beautiful that motivates me. Othertimes, it's personal pleasure. In the case of my Marquee Clock project, I am working on that clock for the pleasure of seeing my daughter's reaction to it. She's my client.
     
    Personal projects are like workouts. They give me a reason to exercise my skills so that I can see how effective I am right now.  I can then explore, experiment and improve how I implement various solutions.
     
    Ultimately, practice makes perfect.
  5. Like
    zeke got a reaction from dubnet in What is "our" time worth ?   
    That gets me thinking about fees.
     
    If a friend invites me to tackle his problem and I know that I have to climb a learning curve to solve his problem then maybe this would be one of those projects that ought to be done Pro Bono. 
     
    If a friend invites me to tackle his problem and I know the solution already then this would be a project that I charge full price for.
     
    Thoughts or reactions?
  6. Like
    zeke reacted to yyrkoon in What is "our" time worth ?   
    @@dubnet
     
    Sure, I understood that when I asked how often others have to research on the job, for the job. But no, If I do not at least feel competent at a job, I wont make a bid for a job. That does have me wondering how many people actually will take up such a job, and then learn while doing that job. Which is exactly what I did when I contracted security work. As there was no way I could tell the client 100% that I could fix their system(s), but I was very experienced at doing just that.
     
    The problem with building embedded systems is that a potential project can potentially span several "discipline" so there is no way in hell anyone can know *everything*. Here, what I find myself realizing this is more of a game of knowing *if* something is possible, rather than knowing how something is possible. Then it just becomes a game as to whether one can assimilate the needed information fast enough to complete a project in a timely fashion . . .For many smaller projects I'm fairly confident I can compete reasonably well. But for larger projects, deciding whether you can compete or not gets a bit more hazy. At least it does for me.
  7. Like
    zeke reacted to yyrkoon in What is "our" time worth ?   
    It sounds like perhaps we're alike in the regard then. Certainly you know stuff I do not, but I'm also sure the opposite is true.
     
    One aspect I typically do better than most is knowing Linux very well. This does not mean I know everything, but usually if someone were to ask me *if* a thing were possible, I'd know right away. And then perhaps even offer more than way to achieve said goal. In some cases it's from 30k feet, as I not have personally done exactly what is being discussed. But very seldom have I not been able to do something discussed in this context.
     
    A perfect example would be this very simple GPIO / peripheral "library" I'm writing using Nodejs( javascript ) for the beaglebone. Prior to writing the code myself I did not know exactly how to do specific things. but I knew they were possible, and even discussed this with others many times from a high level. So in the context of if this were a job . . . someone would be paying me 50 /hr basically to research, and write code. While only paying me for a fraction of my actual time spent on the project.
     
    EDIT:
     
    Oh and if someone were paying e to write the library Im writing now. It'd be  done already heh Instead of me writing some code as a proof of concept to myself, and then watching 2-3 hours of game of thrones, or sons of anarchy, or whatever
  8. Like
    zeke got a reaction from OpalApps in What is "our" time worth ?   
    One time, I made an estimate and it ended being way off because I hadn't accounted for the time I would need to create a test jig to properly simulate communications between the target I was designing and the client's existing hardware. That was a whole new chunk of electronics that I had to assemble, program and test. I had to eat a bunch of that time and not charge for it. The customer and I had a lot of long conversations during that project.
     
    I have learned from that oversight. It was not intuitively obvious at the beginning but it had to be done. I know better now.
     
    To guard against this from happening again, I am developing a pseudo generic dev board + PC software that allows me to simulate  communication between the target system and the rest of the client's system.  
     
     
    Do I know everything? Nope. Not even close. So, most times, the work demands you to perform research. I will and do charge for that but I let the client know in advance. I consider it as part of the initial project assessment checklist. I classify this as a combination of due diligence, quality control, professionalism and pride of workmanship.
     
    Nobody is perfect but we can be true to our intentions.
  9. Like
    zeke got a reaction from dubnet in What is "our" time worth ?   
    One time, I made an estimate and it ended being way off because I hadn't accounted for the time I would need to create a test jig to properly simulate communications between the target I was designing and the client's existing hardware. That was a whole new chunk of electronics that I had to assemble, program and test. I had to eat a bunch of that time and not charge for it. The customer and I had a lot of long conversations during that project.
     
    I have learned from that oversight. It was not intuitively obvious at the beginning but it had to be done. I know better now.
     
    To guard against this from happening again, I am developing a pseudo generic dev board + PC software that allows me to simulate  communication between the target system and the rest of the client's system.  
     
     
    Do I know everything? Nope. Not even close. So, most times, the work demands you to perform research. I will and do charge for that but I let the client know in advance. I consider it as part of the initial project assessment checklist. I classify this as a combination of due diligence, quality control, professionalism and pride of workmanship.
     
    Nobody is perfect but we can be true to our intentions.
  10. Like
    zeke reacted to dubnet in What is "our" time worth ?   
    Having been at this for over 20 years I have found that setting a rate can be part art, part science.  Obviously it depends on a lot of factors (e.g. type of market, competitors, value delivered, customer perception of value delivered, etc.). Like @@Fmilburn mentioned in an earlier post, in the end the rate needs to strike a fair balance between the buyer and seller.
     
    Long ago I had an acquaintance who provided similar services to mine. He constantly complained about mistreatment/disrespect from his customers, with a good number who hadn't paid him.  His rate was less than half of what I charged. When he asked what he could do about it I advised him to significantly increase his rate which would do two things. It would scare off the customers looking for the lowest possible cost (the same ones that didn't pay and typically were the most problematic/difficult customers). It would also create a perception of value with the remaining customers as long as he was delivering value commensurate with his rate.  Unfortunately, he didn't heed the advice. His business faltered and he now works for someone else.
     
    One of the things I have done in the past, if entering a new market, is to assess what competitors that provide similar services as we do charge for their services. Provided there are enough of them in the market to yield enough data points to be meaningful, I can position our services at a price point that reflects both the marketplace as well as the unique value we provide in the context of that marketplace. However, in the end I probably still don't charge enough.
     
    One caveat though, after looking at the market rate, is if all your competitors are living in the back of their vans your cost structure may kill you.  Even after arriving at a market rate you still have to look at all your costs, both hard costs and your time. I have found that doing a post mortem on projects, where you have tracked every minute of your time (billable and non billable), can be a real eye opener in terms of your "real" (now diluted) hourly rate.  With this information you can determine if what you are providing to the market will be truly fruitful to you or not.
  11. Like
    zeke got a reaction from tingo in What is "our" time worth ?   
    @@yyrkoon
     
    The price all depends upon the situation. If the person gives me the vibe that they are a risk of not paying then the price is high.
     
    I want them to know that I am a Professional Engineer.
     
    I've been burned in the past by someone who contacted me via this website. I was not paid for 12 hours of my time. I have chosen to never let that happen again. 
     
    For my own reasons, I have not revealed that person's identity to the rest of this community because I believe that they are not a regular here. They know how much of a flake they are. They don't need me to shout it from this rooftop. 
     
    I honestly hope they never come back to this website ever again. 
    ?_? 
     
     
     
    On the topic of the price, here are my thoughts. I have an initial one hour phone conversation with the person and make an initial assessment of the scope of work. I figure out these things:
    Do I have all the resources needed to solve this person's problem? Do I have the skills to solve this person's problem? Do I have the time to solve this person's problem? Does the person have the time to wait for my solution? Does this person have the authority to solve this problem for him? Does this person have the money to pay for my solution? What does the solution look like? Where can compromises be made in the solution? Can logical milestones be found for the work deliverables? Essentially, what are the risks and rewards for both parties in this work effort?
     
    If the time required to complete the project is long then I can afford to lower the hourly rate. If the time is short to complete then I usually increase the price somewhat.
     
    Depending upon the relationship that develops between both parties, the payment style can be established i.e.: Lump Sum vs Hourly vs Value Based.
     
    If is my opinion that the best example of Value Based pricing is where I create a solution for a client then sell that client many units. In that case, I retain the ownership of the IP.
     
    In the case of Lump Sum or Hourly pricing, it is my belief that the customer has a right to ask for ownership of the IP. That IP must be paid for though. There is a lot of wiggle room in this instance i.e.: How much of the IP and how much you charge for it is up for discussion. You have control over what is on the negotiating table.
     
     
    The Project Assessment Agreement is my way of initially building trust between two trustworthy parties. It's my way of saying "This is what I am thinking. If you are thinking the same thing then we can do business together. If not then please go away in peace."
     
    After the PAA has been completed, a formal contract must be written before the work on the complete project can commence. 
     
    The formal contract will spell everything out in gloriously, painful detail so that both parties are keenly aware of the expectations they have agreed to meet.
     
    Does that answer the question?
     
    By the way, this is a good discussion. I like it.
       
     
  12. Like
    zeke got a reaction from yyrkoon in What is "our" time worth ?   
    @@yyrkoon
     
    The price all depends upon the situation. If the person gives me the vibe that they are a risk of not paying then the price is high.
     
    I want them to know that I am a Professional Engineer.
     
    I've been burned in the past by someone who contacted me via this website. I was not paid for 12 hours of my time. I have chosen to never let that happen again. 
     
    For my own reasons, I have not revealed that person's identity to the rest of this community because I believe that they are not a regular here. They know how much of a flake they are. They don't need me to shout it from this rooftop. 
     
    I honestly hope they never come back to this website ever again. 
    ?_? 
     
     
     
    On the topic of the price, here are my thoughts. I have an initial one hour phone conversation with the person and make an initial assessment of the scope of work. I figure out these things:
    Do I have all the resources needed to solve this person's problem? Do I have the skills to solve this person's problem? Do I have the time to solve this person's problem? Does the person have the time to wait for my solution? Does this person have the authority to solve this problem for him? Does this person have the money to pay for my solution? What does the solution look like? Where can compromises be made in the solution? Can logical milestones be found for the work deliverables? Essentially, what are the risks and rewards for both parties in this work effort?
     
    If the time required to complete the project is long then I can afford to lower the hourly rate. If the time is short to complete then I usually increase the price somewhat.
     
    Depending upon the relationship that develops between both parties, the payment style can be established i.e.: Lump Sum vs Hourly vs Value Based.
     
    If is my opinion that the best example of Value Based pricing is where I create a solution for a client then sell that client many units. In that case, I retain the ownership of the IP.
     
    In the case of Lump Sum or Hourly pricing, it is my belief that the customer has a right to ask for ownership of the IP. That IP must be paid for though. There is a lot of wiggle room in this instance i.e.: How much of the IP and how much you charge for it is up for discussion. You have control over what is on the negotiating table.
     
     
    The Project Assessment Agreement is my way of initially building trust between two trustworthy parties. It's my way of saying "This is what I am thinking. If you are thinking the same thing then we can do business together. If not then please go away in peace."
     
    After the PAA has been completed, a formal contract must be written before the work on the complete project can commence. 
     
    The formal contract will spell everything out in gloriously, painful detail so that both parties are keenly aware of the expectations they have agreed to meet.
     
    Does that answer the question?
     
    By the way, this is a good discussion. I like it.
       
     
  13. Like
    zeke got a reaction from tingo in What is "our" time worth ?   
    @@yyrkoon
     
    I've been self employed since 2005. I could tell you my stories.
     
    For me, the answer to this question is the most important: What do I want?  My answers typically cover the range from selfish to selfless.
     
    The latest craze amongst the self-employed is value based pricing. It's a tricky thing to pull off if you haven't got lots of experience writing proposals and contracts. I haven't done it myself. I usually just charge a high fee.
     
    Here's a copy-paste of my Project Assessment Agreement that I give to all new prospective clients. This is my tool to figure out if the work is worth the effort required.
     
    =======
    Project Assessment Agreement
    The purpose of the project assessment agreement is to equally establish expectations of both you (the client) and Nine Micron Inc.
     
    Minimum deposit is $1000 which covers the first four hours payable in advance.
     
    Work will continue to a maximum of eight hours which caps the assessment fee at $2000.
     
    If the assessment takes the full eight hours then the fee is due upon delivery of the report.
     
    Work proceeds when all necessary information is provided or otherwise obtained.
     
    The assessment phase will result in:
    A summary of the problems at hand, A description of all possible solutions and, An assessment of the risks and rewards of each possible solution. Process Flow Steps:
    Define the objective. List out all possible successful solutions. Decide which solution to use. Explain why that choice is the best one. Test the solution and collect data to prove that the solution is in fact successful. =========
     
    Another benefit of this tool is to weed out the people who will not value your services. It works well to reduce your initial risk and establishes that you are in control on the work effort.
     
     
    Feel free to copy, edit, modify and use it too suit your needs.
     
    I hope it helps even a little bit.
     
     
     
  14. Like
    zeke got a reaction from dubnet in What is "our" time worth ?   
    @@yyrkoon
     
    The price all depends upon the situation. If the person gives me the vibe that they are a risk of not paying then the price is high.
     
    I want them to know that I am a Professional Engineer.
     
    I've been burned in the past by someone who contacted me via this website. I was not paid for 12 hours of my time. I have chosen to never let that happen again. 
     
    For my own reasons, I have not revealed that person's identity to the rest of this community because I believe that they are not a regular here. They know how much of a flake they are. They don't need me to shout it from this rooftop. 
     
    I honestly hope they never come back to this website ever again. 
    ?_? 
     
     
     
    On the topic of the price, here are my thoughts. I have an initial one hour phone conversation with the person and make an initial assessment of the scope of work. I figure out these things:
    Do I have all the resources needed to solve this person's problem? Do I have the skills to solve this person's problem? Do I have the time to solve this person's problem? Does the person have the time to wait for my solution? Does this person have the authority to solve this problem for him? Does this person have the money to pay for my solution? What does the solution look like? Where can compromises be made in the solution? Can logical milestones be found for the work deliverables? Essentially, what are the risks and rewards for both parties in this work effort?
     
    If the time required to complete the project is long then I can afford to lower the hourly rate. If the time is short to complete then I usually increase the price somewhat.
     
    Depending upon the relationship that develops between both parties, the payment style can be established i.e.: Lump Sum vs Hourly vs Value Based.
     
    If is my opinion that the best example of Value Based pricing is where I create a solution for a client then sell that client many units. In that case, I retain the ownership of the IP.
     
    In the case of Lump Sum or Hourly pricing, it is my belief that the customer has a right to ask for ownership of the IP. That IP must be paid for though. There is a lot of wiggle room in this instance i.e.: How much of the IP and how much you charge for it is up for discussion. You have control over what is on the negotiating table.
     
     
    The Project Assessment Agreement is my way of initially building trust between two trustworthy parties. It's my way of saying "This is what I am thinking. If you are thinking the same thing then we can do business together. If not then please go away in peace."
     
    After the PAA has been completed, a formal contract must be written before the work on the complete project can commence. 
     
    The formal contract will spell everything out in gloriously, painful detail so that both parties are keenly aware of the expectations they have agreed to meet.
     
    Does that answer the question?
     
    By the way, this is a good discussion. I like it.
       
     
  15. Like
    zeke reacted to greeeg in What is "our" time worth ?   
    From @@zeke's wording of the agreement it sounds like it's more an initial consultation fee.
     
    Taking on new projects is tricky, and in his own words
     
    Of course you need to uphold the value of your services in the work output you present
  16. Like
    zeke reacted to yyrkoon in What is "our" time worth ?   
    @@zeke
     
    So I have a question that I have to ask. $250 / hr ? I charge $50 / hr for a flat hourly rate. Minimum 1 hour. So, if you do not mind answering . .  why so much ? No judgment here, I'm just curious why.
  17. Like
    zeke reacted to yyrkoon in What is "our" time worth ?   
    I think I'd rather hear if from the "horses mouth". As I can think of several possibilities as to why<whatever>, but it's the <what have i not thought about> that I'm looking for.
  18. Like
    zeke got a reaction from dubnet in What is "our" time worth ?   
    @@yyrkoon
     
    I've been self employed since 2005. I could tell you my stories.
     
    For me, the answer to this question is the most important: What do I want?  My answers typically cover the range from selfish to selfless.
     
    The latest craze amongst the self-employed is value based pricing. It's a tricky thing to pull off if you haven't got lots of experience writing proposals and contracts. I haven't done it myself. I usually just charge a high fee.
     
    Here's a copy-paste of my Project Assessment Agreement that I give to all new prospective clients. This is my tool to figure out if the work is worth the effort required.
     
    =======
    Project Assessment Agreement
    The purpose of the project assessment agreement is to equally establish expectations of both you (the client) and Nine Micron Inc.
     
    Minimum deposit is $1000 which covers the first four hours payable in advance.
     
    Work will continue to a maximum of eight hours which caps the assessment fee at $2000.
     
    If the assessment takes the full eight hours then the fee is due upon delivery of the report.
     
    Work proceeds when all necessary information is provided or otherwise obtained.
     
    The assessment phase will result in:
    A summary of the problems at hand, A description of all possible solutions and, An assessment of the risks and rewards of each possible solution. Process Flow Steps:
    Define the objective. List out all possible successful solutions. Decide which solution to use. Explain why that choice is the best one. Test the solution and collect data to prove that the solution is in fact successful. =========
     
    Another benefit of this tool is to weed out the people who will not value your services. It works well to reduce your initial risk and establishes that you are in control on the work effort.
     
     
    Feel free to copy, edit, modify and use it too suit your needs.
     
    I hope it helps even a little bit.
     
     
     
  19. Like
    zeke got a reaction from greeeg in What is "our" time worth ?   
    @@yyrkoon
     
    I've been self employed since 2005. I could tell you my stories.
     
    For me, the answer to this question is the most important: What do I want?  My answers typically cover the range from selfish to selfless.
     
    The latest craze amongst the self-employed is value based pricing. It's a tricky thing to pull off if you haven't got lots of experience writing proposals and contracts. I haven't done it myself. I usually just charge a high fee.
     
    Here's a copy-paste of my Project Assessment Agreement that I give to all new prospective clients. This is my tool to figure out if the work is worth the effort required.
     
    =======
    Project Assessment Agreement
    The purpose of the project assessment agreement is to equally establish expectations of both you (the client) and Nine Micron Inc.
     
    Minimum deposit is $1000 which covers the first four hours payable in advance.
     
    Work will continue to a maximum of eight hours which caps the assessment fee at $2000.
     
    If the assessment takes the full eight hours then the fee is due upon delivery of the report.
     
    Work proceeds when all necessary information is provided or otherwise obtained.
     
    The assessment phase will result in:
    A summary of the problems at hand, A description of all possible solutions and, An assessment of the risks and rewards of each possible solution. Process Flow Steps:
    Define the objective. List out all possible successful solutions. Decide which solution to use. Explain why that choice is the best one. Test the solution and collect data to prove that the solution is in fact successful. =========
     
    Another benefit of this tool is to weed out the people who will not value your services. It works well to reduce your initial risk and establishes that you are in control on the work effort.
     
     
    Feel free to copy, edit, modify and use it too suit your needs.
     
    I hope it helps even a little bit.
     
     
     
  20. Like
    zeke got a reaction from Fmilburn in I'm struggling with the CC3200   
    Relevant Comic
  21. Like
    zeke got a reaction from spirilis in I'm struggling with the CC3200   
    Relevant Comic
  22. Like
    zeke reacted to tripwire in SensorTag Altitude Logger   
    Recently I took a trip to the US, which offered a good opportunity to test my altitude logger by recording a profile of the whole journey there. The trace revealed some interesting details about the flights I took, and airline operations in general.

    Here's the profile for the entire trip:
     

     
    The x-axis shows elapsed time in minutes. The altitude is shown in metres, measured relative to the start of the trace (not too far above sea level). Despite that I'll be using feet as the unit of altitude here, since that's the standard used in aviation. Because the logger calculates altitude based on air pressure, it is affected by cabin pressurisation. Instead of recording the true altitude of the aircraft it gives a trace of the effective altitude inside the cabin.

    The first big peak at the blue cursor is a flight from Edinburgh to London Heathrow. Comparing the cabin altitude trace against real altitude data makes it easier to pick out the main features, so here's a chart showing this flight's altitude as broadcast over ADS-B:
     

     
    And this is a closeup showing what my altitude logger recorded for the same flight:
     

     
    The cursors mark where I think the flight started and finished, based on the fact that the plane was in the air for 70 minutes. From takeoff the pressure falls steadily until the effective altitude in the cabin is about 7000ft, at which point the aircraft is actually at 37000ft. After cruising there for 12 minutes the plane descends and cabin pressure steadily increases.

    The cabin pressure reaches ground level before the plane actually lands, so the trace stays flat for the next 12 minutes. In fact, this section of the trace is effectively below ground level while the plane approaches landing. The plane's environmental control system has deliberately overshot and pressurised the cabin to higher than ambient pressure at the destination. At the orange cursor marking the end of the flight you can see a slight increase in altitude. This is when the flight is over and the controller opens the pressurisation valve to equalise with the external air pressure.

    It seems this extra pressurisation is done before takeoff and landing to help the system maintain a steady pressure. There's a detailed explanation of the reasons for this here: http://aviation.stackexchange.com/questions/16796/why-is-cabin-pressure-increased-above-ambient-pressure-on-the-ground

    Now on to the second flight, which was from Heathrow to Dallas Fort Worth. First the ADS-B trace:
     

     
    And the altitude logger's version of events:
     

     
    Again, the cursors mark the start and end of the flight and line up with the reported duration. The "steps" along the top of the trace match up with changes in cruise altitude from 32000?>34000?>36000ft. Maximum effective cabin altitude is about 5500ft, lower than the first flight even when the lower cruise altitude is taken into account. I think that's down to the use of a newer 777 on the international flight compared to the A319 on the domestic route. Modern planes are increasingly designed to offer lower effective cabin altitudes for passenger comfort.

    The stepped flight profile is used to maximise fuel efficiency. Flying higher reduces losses to air resistance, but early in the flight the aircraft is heavy with fuel and climbing is expensive. As the fuel is burned off the optimal cruise altitude increases, so ideally the plane would climb to match. In fact the plane can't climb gradually because modern air traffic control regulations restrict aircraft to set flight levels. The best option under these restrictions is to perform a "step climb" up to a higher level when it's more fuel-efficient than the current one. The flight levels are multiples of 2000ft for flights from the UK to the US, which is why the steps are 32000->34000?>36000ft.

    Wrapping up, one of the things I hoped to test by recording this journey was high rates of altitude change. The altitude logger can currently handle rates of change up to
  23. Like
    zeke got a reaction from spirilis in Digital Ocean?   
    I've got my droplet up and running now.
     
    It felt good to dust off the linux admin skills and set everything up.
     
    Here's a screen shot of the speed comparison between my old and new service provider.
     

     
    That's the trigger point for me. Speed. And this is running on their $5/month configuration!
     
    I now like these new guys. Here's my referral link if anyone else wants to try out Digital Ocean for themselves.
     
     
    PS: @@bluehash, I encountered the dreaded myslq crash this morning. I've got it sorted out already. We should compare notes.
     
  24. Like
    zeke got a reaction from tripwire in Digital Ocean?   
    I've got my droplet up and running now.
     
    It felt good to dust off the linux admin skills and set everything up.
     
    Here's a screen shot of the speed comparison between my old and new service provider.
     

     
    That's the trigger point for me. Speed. And this is running on their $5/month configuration!
     
    I now like these new guys. Here's my referral link if anyone else wants to try out Digital Ocean for themselves.
     
     
    PS: @@bluehash, I encountered the dreaded myslq crash this morning. I've got it sorted out already. We should compare notes.
     
  25. Like
    zeke reacted to Apr30 in Digital Ocean?   
    While I was doing research on this I came across Vultr and Scaleway. Don't have any experiences with them, though.
     
     
    Vultr
    * https://www.vultr.com/pricing/
    * 15GB SSD, 768MB RAM
    * 1T Traffic
    * USD 5 + VAT
     
     
    Scaleway
    * https://www.scaleway.com/pricing/
    * 50GB SSD, 2GB RAM
    * Unlimited Traffic
    * 2.99 EUR + VAT
×
×
  • Create New...