(Personally I think whistle blowers are an important part of applying transparency and checks to companies & governments, just some of the information merchants aren't the nicest of people.)
569 karma · joined February 27, 2015
(Personally I think whistle blowers are an important part of applying transparency and checks to companies & governments, just some of the information merchants aren't the nicest of people.)
Companies will try to only pay staff more when they can justify that to the shareholders as being a way to make more money for the shareholders. A public company exists solely for the benefit of the shareholders and all actions stem from that.
Many businesses have very small profit margins, so paying staff more or training staff could turn them unprofitable.
When you're buying products cheaply it's likely that somebody (or someone's environment) is paying a price for it. Once you bear that in mind there is such a thing as products being uncomfortably cheap.
(I live in Norway where nothing is cheap but almost everyone earns a good wage. The result is that people don't buy so much stuff but lead good lives.)
That I can recognise I see a LOT of Nissan Leafs and good number of Hyundai Ioniq, Kia Soul, VW e-Golf, BMW i3 and for businesses the Nissan e-NV200 and Renault Kangoo vans. There are other models out there, Oslo being a good market for electrics.
It's common here for people who were early to order a popular electirc car (like the Ioniq or Opel Ampere) to be able to sell it as 'used' for more than you can buy one new from the dealership that you have to wait months for.
Another problem for Tesla is having only 5 quarters of positive cashflow out of 35. A single quarter hints at a turn around but there needs to be several positive quarters in a row to prove that it's not just an accounting trick (e.g. by counting more income in the quarter and delaying payments & write downs).
Don't get me wrong, I'm not anti-Tesla, but living in Oslo I see a lot of electric cars and Teslas are no longer the majority. Plus the Tesla repair workshop near me is always full, which isn't a great sign!
Sure, if they crash they're more likely to get a head injury that the public purse has to pay for. But that theoretical amount is probably tiny compared to all the dumb stuff everyone else in the country is doing that contributes towards healthcare costs.
Laws and state support are both about finding the impossible balance between control, freedom, responsibility and cost.
If there was an easy and consistent answer to pricing models a lot more people would still be in business! Especially for a hobby based service. I don't know how much market research you've done but even asking on forums would be a good way to get an idea. Monthly commitments are full on for people to make. How about bundles of uses? Like 10 uses for a few dollars?
You might need to do more to drive people to the free version to try before they buy. Have you considered different payment plans, like one offs?
Also when an image is uploaded it'd be good if the image aspect ratio was preserved so that it isn't distorted.
What people think depends upon perspective. US tech companies are in the news more but there are unicorns and big tech companies in Europe, some of which I couldn't tell you what they do. As well as many large older IT companies there are also big new tech companies like Spotify, ASOS, Just Eat, skyscanner, Deliveroo. All big, all tech, all headquartered or started in the EU recently.
This is also ignoring the current shift to offshoring development to Europe. Eastern Europe is getting the lion's share of that but the western side is home to a lot of big divisions of international companies.
It does like you have the tech blinkers on, which happens to a lot of people working in tech. "Tech is the future and tech is everything." People tend to forget that the traditional industries are massive (the biggest companies in the world by revenue aren't tech companies) and they tend to play a larger role in a country's economy that tech does. These are companies that build their own towns if they need to and cause massive effects when they move.
Manufacturing is huge and ultimately everything tech uses is a product of manufacturing. Foxconn is as much a manufacturer as a tech company. The biggest companies working on self driving cars are the traditional car manufacturers, including European giants Volkswagen and Daimler. Other players like Uber use other people's cars. And when these cars go on sale half or more of the profit will be to the company that makes the metal.
Finally, a large part of Trump's promises were to bring back these old industries to the US because they're the industries that create long term jobs and transform towns.
The Economist sums it up: “While quotas have not been the calamity that many had feared, they have also so far failed to achieve what governments had promised they would.“ https://amp.economist.com/business/2018/02/17/ten-years-on-f...
Social enterprises aren’t responding to a market opportunity in the same way a for profit business is. They are filling a gap that the for-profit market has created or left unfilled and are often doing so by using fragile mechanisms that can easily be destabilised. They don’t really have many options to adapt and they can’t ‘pivot’ to a new customer base to adapt as that would be leaving the original problem unsolved.
In short, I don’t think you can fairly use free market thinking for social enterprises.
I think they were actually hoping less people would throw bottles away but it’d have to be a lot higher to stop that.
I'm British but recently moved to Oslo, Norway. Until recently I worked at a start-up incubator where there was talk about the 'extreme' start up work life. For Norwegians that meant that they left the office at 5pm instead of 3:30 or 4pm. By 6pm the hot desk office space was normally empty and the lights switched themselves off.
It's a tiny industry here and no-one is looking to build the next facebook, they're just looking to do interesting work whilst also having a good life.
Ultimately correlation isn't causation. Working 40 hours doesn't guarantee success by itself and neither does waking up at 4am.
I like some conversational podcasts like After On where they tend to stick to discussing the topic at hand but I couldn't get into Stuff You Should Know or Joe Rogan as there was a lot of general chat in there or not high enough information density.
I don't want to hear 5 minutes of why somebody thinks something is worth doing a podcast on: just tell me the interesting stuff and I'll judge for myself.
Once a company takes on a lot of debt or VC capital it has to constantly chase its next round of funding above all else; once it IPOs it has to constantly chase a higher share price above all else. The actual profitability of a company seems to rarely a factor in either of these but hype always is.
For a company success should be making a profit, treating your employees well and making something worthwhile.
Learn Modern ColdFusion (CFML) in 100 Minutes: https://modern-cfml.ortusbooks.com/
Learn CF in a Week: http://www.learncfinaweek.com/
CF Docs: https://cfdocs.org/
TryCF (in browser CodePen style): https://www.trycf.com/
There's a lot of built in security to Lucee/CF but for a query I'd always be doubly sure and explicitly state the parameter data type as well and that'll definitely block SQL injections. So this code would be:
queryExecute( "select * from employee where id= :itemID" { itemID = { value=arguments.itemID, cfsqltype="cf_sql_varchar", list=true } } );
For me the article's negative was that it focused on one edge case reason to not use IDs, when there are others.
While everyone makes mistakes I'd hope that using an array's size instead of its value is nigh on impossible to end up committed, let alone deployed to production.
As everyone makes mistakes for me the main reason for not using numeric user ids is because you're much more likely to accidentally expose an API or query string param that can be used to look up other user ids. When that happens being able to enumerate ids makes for a massive data breach, whereas a GUID stops that.
(There may be some reason why you'd be forced to use numeric IDs in a data store for performance at scale reasons but I imagine that's relatively rare.)
The result of networking apps is some sales people generate a lot of very low quality leads at the expense of the event's reputation as most delegates don't want spam.
For messaging apps 99% of messages will be sent by 1% of delegates: the pushy sales people. "Hey, want to meet to discuss my amazing product!"
As you say, another option is is "tell me who I was talking to" but again the sales people pollute that experience. B2B events are about selling but there are sales teams who'll scan your badges as they're saying hello (electronically or visually) and then email you forever afterwards. I imagine that "tell me who I stood near" would result in sales teams walking around the entire venue, on the lookup for anyone that looks important to loiter near. Or they could just hide a device in the toilet and get everyone ;)
We tried allowing delegates to build a contact list to message and then also notify when those people were at the same networking event just once. It really wasn't much value to anyone other than, you guessed it, pushy sales people that our VIPs would rather have avoided.
I don't know if it's still the same but Grip's "tinder for events" used to rely on both parties showing mutual interest before allowing communication. That's the best mechanism that I know of but I wouldn't be surprised if the messaging connection rate was incredibly low.
It’s fine to start a business in an industry you’re not crazy about but most people who make a success this way know there’s a ready and waiting market to earn money in with an existing product. People need plumbers and roofs need tiling.
Most “start-ups” should be founded on the principle of “We’ve identified a problem and we’re the best people to provide the solution” and even then most of them fail. Even pivots are based on that principle (“what we built didn’t solve a problem but we identified another problem we can solve”).
It sounds like you’re gone the route of “I’ve identified a market that I want to provide a solution for.” The events industry is big, which means there are a lot of people thinking the same. During my time I integrated our system with several companies that no longer exist. Many of these products didn’t solve actual attendee or organiser problems or desires and so uptake or return was very low.
Attendee needs are fairly simple and limited (easy to buy tickets, get information about what’s on, and easy conference experience) and they rarely want anything more (e.g. only a tiny fraction or marketing types actually want networking apps).
Conference organiser needs are many and they want to use as few suppliers as possible as each additional supplier means extra work on integration. So most of the businesses doing well in the event space are companies that can provide a large, near holistic product for them which covers a lot of needs. So to complete against them you’ll need a lot more resources than it sounds like you do.
Reading between the lines it sounds like you already know what you need to do. If you’ve lost the drive and conviction that this will be a success then and unless you can find a real problem you can build and sell a solution for quickly and easily, then it’s probably time to call it a day. Try again in a bit and if possible without the pressure of money from family and friends.
I worked in the technology side of large B2B events for about 10 years and there are certainly people who get really excited about B2B events!
You don't have to LOVE your product or industry but you've got to be interested in the industry and believe in your product. Being disinterested in the industry is a big disadvantage. Most people coming up with ideas or solutions are deeply involved in their industry and interested enough to spend a lot of time thinking about it.
If getting such dangerously awful code deployed to production is likely then sequential IDs are just one of your many problems!
Sequential IDs for key data can be good to avoid for a few good reasons but awful code isn't one of them. Testing, code reviews and not having bad programmers should be in place to fix that.