151 karma · joined June 13, 2011
I've seen this devolution happen at least three times in my career at three different companies. In every case, it results in devaluation, then exploitation, then burnout of previously enthusiastic, talented developers who soon leave. Sadly (even if you are a staunch capitalist in the executive suite) this "streamlining" almost always proves misguided as the company inevitably loses all technical credibility, innovation stalls and it loses any competitive edge it might have had along with market share.
I could see no obvious way to set outline/stroke width or color for shapes even though art in the library show those properties. There seems to be no way to rotate shapes. There are no line or text tools.
Of course, your art library isn't fully populated yet. For instance, search for "dog", "bird", "dragon", "knight" all return no results. Also, even though the search tool asks for submitted art, it wasn't at all clear how to submit it.
Anyway, the idea of sharing and collaborating around images in a simple environment is appealing. With a few tweaks, it would be something that I would use and recommend.
I've had the most success with this formula:
1. Every day, wake early and work on your project 1 - 2 hours.
2. Work your "day" job. If your job allows it, spend your breaks planning your side-project work.
3. Spend time with family and work some after dinner. In my case, I can usually code
and watch TV out of one eye while spending time with my wife.
4. Rinse and repeat
I used to strongly believe that side projects could only be done in four hour blocks of time without distraction but, often, that kind of time is in rare supply. However, when I got a job that required an hour train commute, I found that I could knock out some useful code even when my time between laptop-open and laptop-closed was 30-45 minutes. The tricks to making use of short blocks of time are: 1) Break the project into short, deliverable bits
2) Build placeholders/stubs as you go for things to flesh out later
3) Leave yourself lots of "do this later" comments with ample specifics.
Don't just say "finish this." Say "Use ABC parameter to lookup XYZ value to override the default."
Structuring the work for "resume-ability" makes it possible to squeeze short bursts of productive work into your day.Yahoo has proven over and over that they don't understand community or know how to capitalize on crowd wisdom. After Yahoo took over del.icio.us, they didn't know what to do with it despite it being a huge trove of valuable data: 1) desirable, tagged sites, 2) the social network, and 3) the tags/interests of del.icio.us users.
Yahoo made similar blunders when it acquired Flickr, alienating its most active users.
It works fairly well with the two obvious limiting factors are screen size and clunky keyboard input. However, the #1 stumbling block is lack of cursor navigation. It desperately needs cursor keys and shortcuts to move to the beginning/end of the line. The #2 greatest frustration is having no good way to select text except fat finger selection.
What's needed most is an extended keyboard (w/ cursor keys, for example) and/or a smarter popup "magnifying glass" mode so you have a bigger target for fat finger selections.
TechCrunch - http://feeds.feedburner.com/TechCrunch/
BetaNews - https://betanews.com/rss
SlashDot - http://rss.slashdot.org/Slashdot/slashdotMain
TechMeme - https://www.techmeme.com/feed.xml
MIT Technology Review - https://www.technologyreview.com/topnews.rss
Wired News - https://www.wired.com/rss/
Eureka Alert! - https://www.eurekalert.org/rss.xml
Here's an article about RSS and its fall from grace: https://twobithistory.org/2018/09/16/the-rise-and-demise-of-...
What's sad is that RSS was once the powerhouse of social sharing for most of a decade, giving blogs and websites a huge reach to rival any centralized and siloed platform like Facebook or Twitter.
From that you directly get other key concepts:
OOP principles (minus inheritance): What objects hide is as important as what they expose.
Test-Driven-Development: Code the test, then fix the code to pass the test.
Build only what you need: Components should be as simple as possible but no simpler. Keep the future in mind but don't build future features until they are needed (and better understood).
First, you should structure your resume as a "skills resume" that includes as many languages, environments and major libraries as you know how to use.
Then, include your strongest, most relevant school/personal projects and list them with action verbs, "Built XXX using YYY with these features...", "Designed ZZZ with algorithm QQQ..."
Most employers are looking for entry-level developers that have built complete solutions and not toy problems. They want to know that you can collaborate with others and contribute. Underscore any and all school/volunteer projects that show that.
BTW: I gave that same advice to my nephew who was self-taught without any college degree to get his first development job. What helped him the most, I think, was that he essentially created his own first job, so to speak, by building a basic scheduling web app for a friend's bike messenger service (for free). It filled a gap in his resume and proved that he could turn requirements into working code. That's all he needed to get a "real" job.
In my experience, you'd consider yourself lucky to work for a company that sees I.T. as a strategic/operational advantage (and not merely a "cost center") and therefore pays its staff 10% better than market average plus bonuses.
Unfortunately, I've worked for truly "I.T. forward" companies like that and still seen a merger or buyout completely flip the culture. Overnight I.T. salaries and budgets were seen as indulgences and people were laid off or quit in droves.
The one thing I've learned about this industry is that no matter how innovative or adept an engineering department is, an exuberantly stupid executive team can completely squander and destroy that asset surprisingly quickly.
1) I was at the airport (OK, not so hard, maybe using WiFi or GPS). 2) So was my friend's son, Bobby (who I wasn't directly FB friends with). 3) We were at a gate waiting for our plane..
Here's the thing: I hadn't posted any kind of itinerary or booked the flights myself. So, if FB was just "guessing" and did this every time a friend-of-a-friend was at the same place, you'd constantly be paired up with relative strangers crossing paths nearby.
"planned work" is really "prioritized and agreed to" work. "ad-hoc" work is just the urgent priority of (usually) one person.
After years of dealing with the conflict, I've found the easiest answer is always "I'd be happy to give you what you need. Which of these planned tasks from you (or your boss) are you willing to sacrifice or postpone for your urgent task?" 80% of the time that's enough. If not, you walk them over to their boss and ask them the same question. Then, you can go back to your desk and work and let them hash it out or hash it out with your boss to convert this "ad-hoc" request into a "agreed to, planned request."
Using MemPa (which is basically one line of JavaScript), your passwords are always hard to crack, retrievable with one password and yet never stored anywhere so there's no tempting honeypot for hackers to target.
The original article is here: https://hackernoon.com/mempa-a-modern-deterministic-password... (There are links to iOS and Android MemPa apps, too.)
I've also wrapped the algorithm in a single-page web app that you can copy to your own site or thumbdrive to make using the MemPa algorithm easier. https://codepen.io/jones1618/full/eeqBNG/
There are a few modern alternatives, however: [How to Outline Your Ideas with 20 Powerful Tools](https://zapier.com/blog/best-outline-software/)
TextPad isn't technically "old" or "discontinued". It is regularly updated and released version 8.1.2 back in March.
Is bypassing college a viable path in tech? Yes, definitely.
Is college worth it? Hard to say. If you are going strictly to have a piece of paper and learn "job skills", no. If you are going for a wider education, connecting with other people and a world of ideas, absolutely. Those are experiences that I regret doing without.
However, there is one directly career-related reason to get an undergraduate degree: While many tech jobs don't require one (especially in the first few years of your career), many of the jobs you may want mid-career will increasingly require a _graduate_ degree.
For example, you can get pretty far doing User Experience work without a degree but I've noticed that more and more senior UX positions or UX architect positions strongly recommend, if not require, a Master's Degree. Likewise, you could be doing everything required of a Data Analyst at your current job but when you go to apply to other companies for a DA job you will likely be competing with and interviewing with people with graduate degrees.
So, my best "old timer's" advice is: Skipping college could very well be the best strategy for some, at first. After you've settled into a few years of work, though, go to night school and get the degree. That way, a graduate degree will be within reach a few years later when you want to pivot into a different or higher career.
Actually, Task Manager showed 90% of my 8Gb ram being utilized and caching to disk constantly with most of the ram and CPU being hogged by eight(!) Slack threads. This is with Slack minimized and sitting idle.
The fix was to replace the Slack/Electron app and use the browser version instead. That solved it.
Electron is a super cool piece of tech that could enable all kinds of great app development but needs to go on a serious diet first.
So, I like your idea of a developer's union with emphasis on professional standards, EFF principles, etc. It would also be a powerful ally for responding to workplace abuses I've seen such as: 1) excessive, mandatory work hours. I know game developers that are required to work 60-80 hour work weeks and sleep at their desks. 2) outsourcing abuse: Having to manage and train offshore "resources" who become your replacement. 3) Keep-a-good-engineer down syndrome. Organizationally suppressing engineers from advancing so they stay in essential, non-executive roles.
And, if you think that your cushy job is immune to these problems, consider that I've seen nearly every one of these conditions arise (usually after a management change) in otherwise humane companies with positive corporate cultures.
While a union might not prevent every individual abuse, it might provide a check on companies who essentially hold your "cushy job" for ransom while they take advantage of the fact that you are salaried (not paid hourly) and can work from home any day or night.
"An elegant method for resolving collisions in hash tables... It has the rare distinction of being easy to implement and efficient both in theory and practice."
It does an amazing job of packing values into N hash tables so there's very little dead space but lookups are very fast.
Given that since Mindstorms first came out, systems-on-a-chip like Raspberry PI and Arduino are down to $10 or $20 dollars, why hasn't Lego brought its Mindstorm prices down?
I loved, loved, loved Lego as a child and my kids love them still (even my 15-year old) but their prices reflect Scandinavian economics and not middle-class U.S. economics. I've come to dread walking down the Lego aisle at the toy store knowing that I'll have to drop $120 on a non-trivial set. I can't stand the thought that we live in a world where Lego bricks are an elitist toy.
So, does Lego really believe that if I want my kid to play with robotics outside of school, I want to spend as much as an iPad or Chromebook for a one-chip microcontroller? That's just price gouging.
It sounds like XLR8 isn't wrong in that identifies the two main activities of a growing business: 1) Making their bread-and-butter work as efficient as possible and 2) Innovating to multiply opportunities and inefficiencies. In short, a company needs to streamline and explore. But, advocating that the networking and exploration required for #2 is an offline, voluntary activity is foolish, dangerous even.
I've worked in a variety of organizations of different sizes, in different industries and different states of startup or maturity and found one consistent pattern for failing organizations: They start to routinely tell people to "stay in their lane" at work and respond to new ideas with "Sounds great! As soon as these low value, high effort activities are done you can work on those high value, low effort ideas in your spare time." That's the beginning of brain death for a company. The body soon follows.
Instead, strong companies with strong leadership know that it isn't their employees responsibility to be more efficient and productive at low-value, high-effort activities. It is the leadership's responsibility to root out and eliminate those activities either by automating, out-sourcing or de-prioritizing them. The right way to streamline a business is to listen to employees and relentlessly cut, kill, and destroy routine or low-value work.
As you do that, you free up and empower employees and the organization to leverage high-value work in front of them and explore and pursue high-value opportunities on the horizon. In a healthy, growing organization those are everyday (during the day) activities not after-hours, side-projects that force employees to sneak time from work or steal time from their families.
FactCheck.org and Politifact.com are steps in the right direction. I'd like to see a site that entertainingly covers news and issues, references other media but is willing to call bullsh*t on the media and politicians.