Hacker Newsnew | past | comments | ask | show | jobs | submit | majani's favoriteslogin

I presume this is just an Android launcher with an app whitelist and no sideloading, slapped on a generic rebrand of someone else's phone hardware, in the end?

So, great, hardware to solve software problems. This should just be a custom image, like Cyanogen was or something. And where are the music options? I constantly listen to music on my phone, so this is a total dealbreaker. It should have Tidal, YouTube Music, Spotify, etc. They're not distractions; nobody stares at their phone whilst listening to audio.


I think pretty much every software company fails to understand that step 4 means you win. You're done. Close the code editor. You don't need to prove anything anymore. Put the software into maintenance mode, fix bugs, polish it off, make it faster if you can, but stop cramming features.

As a user, I've never in my life said "You know, software XYZ does everything I want it to, but since they don't randomly change the UI and update it with unwanted features every few months, it's 'stale' and I won't use it anymore!"

I feel like everything past step 4 is "Developers gotta develop and designers gotta design" and making changes for change's sake rather than the user's sake.


I’ve been doing web development since the mid 90s. In the beginning it was just plain html files that you would manually ftp (not even sftp) to a web server. Later it was html, css, and JS - but it was still a manual process. Eventually jQuery was added to help since nobody was standards compliant and instead of writing different css/JS for every browser, you just used jQuery and it took care of making it work on every browser. Files were still manually uploaded to the web server. Then came ES5. That led to an enormous floodgate of complexity. Suddenly you were expected to have a build system to transpire code to match the lowest browser specs you would support. Then came more complex front end code via react/Vue. Then came typescript. Then came pipelines like Jenkins. And docker. And serverless architecture. And it is absolutely mind boggling how complicated web development is today when It is still just plain html, css, and JS being delivered to the browser.

A lovely knot to unravel!

First, get everything in source control!

Next, make it possible to spin service up locally, pointing at production DB.

Then, get the db running locally.

Then get another server and get cd to that server, including creating the db, schema, and sample data.

Then add tests, run on pr, then code review, then auto deploy to new server.

This should stop the bleeding… no more index-new_2021-test-john_v2.php

Add tests and start deleting code.

Spin up a production server, load balance to it. When confident it works, blow away the old one and redeploy to it. Use the new server for blue/green deployments.

Write more tests for pages, clean up more code.

Pick a framework and use it for new pages, rewrite old pages only when major functionality changes. Don’t worry about multiple jquery versions on a page, lack of mvc, lack of framework, unless overhauling that page.


http://mavweb.mnsu.edu/howard/Schmidt%20and%20Hunter%201998%...

100 years of industrial psychology. See page three.

   -  General mental ability (Are they smart)

   - Work sample test (of actual work they might do, NOT HAZING/Quizes).

   - Integrity. (Varipus tests available for this)
That gets you > 60% hit rate.

Things that do not work.

   - Reference checks (r 0.26) 

   - experience (years) (r 0.18)

   - Years of education (r .10)

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: